Method for Service Implementation in Network Function Virtualization (NFV) System and Communications Unit

ABSTRACT

Embodiments provide a method, which can implement establishment of an network function virtualization (NFV) network service link. The method includes obtaining, by a first communications unit, a service link rule, where the service link rule is used to indicate service processing that needs to be performed. The method also includes obtaining, according to the service link rule, information about a service link through which a service route passes, where the information about the service link is used to indicate information about a virtualized network function (VNF) through which the service route passes, and the VNF is configured for the service processing; and sending a route and resource configuration request message, where the route and resource configuration request message carries the information about the service link, to request to perform, according to the information about the service link, route and resource configuration for the VNF included in the service link.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2014/073967, filed on Mar. 24, 2014, the disclosure of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present invention relates to the communications field, and inparticular, to a method for service implementation in a network functionvirtualization (NFV) system and a communications unit.

BACKGROUND

With development of communications technologies, a network functionvirtualization (NFV) technology is increasingly mature, and a relateddescription about an NFV architecture is provided in the foreword partof the specific implementation manner part, and details are notdescribed herein.

In an NFV multi-layer complex structure, as a virtual function entity, avirtualized network function (VNF) depends on computation, storage, andnetwork connection capability support provided by a physical resource ofan NFV infrastructure (NFVI) unit. A connection between VNFs is alogical link connection, where multiple VNFs are connected in aparticular order by using a logical link, and can constitute a servicelink for service data processing. However, how to establish an NFVnetwork service link is a problem that currently needs to be resolved.

SUMMARY

Embodiments provide a method for service implementation in a networkfunction virtualization (NFV) system and a communications unit, whichcan implement establishment of an NFV network service link.

To achieve the foregoing objective, the following solutions are providedin the embodiments.

According to a first aspect, a first communications unit is provided,where the first communications unit includes a service link ruleobtaining unit, a service link information obtaining unit, and a messagesending unit, where the service link rule obtaining unit is configuredto obtain a service link rule, where the service link rule is used toindicate service processing that needs to be performed. The service linkinformation obtaining unit is configured to obtain, according to theservice link rule obtained by the service link rule obtaining unit,information about a service link through which a service route passes,where the information about the service link is used to indicateinformation about a virtualized network function (VNF) through which theservice route passes, and the VNF is configured for the serviceprocessing. Additionally, the message sending unit is configured to senda route and resource configuration request message, where the route andresource configuration request message carries the information about theservice link obtained by the service link information obtaining unit, torequest to perform, according to the information about the service link,route and resource configuration for the VNF included in the servicelink.

With reference to the first aspect, in a first possible implementationmanner of the first aspect, the first communications unit furtherincludes an information determining unit, where the informationdetermining unit is configured to: before the service link informationobtaining unit obtains, according to the service link rule obtained bythe service link rule obtaining unit, the information about the servicelink through which the service route passes, determine whether theservice link rule includes the information about the service link; andthe service link information obtaining unit includes: an informationdetermining module, a message sending module, a receiving module, and ageneration module, where the information determining module isconfigured to: if the information determining unit determines that theservice link rule does not include the information about the servicelink, determine, according to the service link rule, a type of the VNFthrough which the service route passes and identification information ofa VNF included in each VNF type in the type of the VNF; the messagesending module is configured to send a query request message, where thequery request message carries the identification information, determinedby the information determining module, of the VNF included in each VNFtype, to request to query, according to the identification informationof the VNF, first information of the VNF included in each VNF type,where the first information is used to indicate a network topology, anode capability, and a status of a network function virtualizationinfrastructure (NFVI); the receiving module is configured to receive thefirst information of the VNF included in each VNF type; and thegeneration module is configured to generate the information about theservice link according to the first information, received by thereceiving module, of the VNF included in each VNF type.

With reference to the first possible implementation manner of the firstaspect, in a second possible implementation manner of the first aspect,the service link information obtaining unit further includes anobtaining module, where the obtaining module is configured to: if theservice link rule includes the information about the service link,obtain the information about the service link included in the servicelink rule.

With reference to the first possible implementation manner of the firstaspect or the second possible implementation manner of the first aspect,in a third possible implementation manner of the first aspect, themessage sending module is configured to: send the query request messageto a second communications unit, to request the second communicationsunit to query, according to the identification information of the VNF,the first information of the VNF included in each VNF type.

With reference to the third possible implementation manner of the firstaspect, in a fourth possible implementation manner of the first aspect,the message sending module is configured to: send the query requestmessage to a VNF manager (VNFM), to send the query request message tothe second communications unit by using the VNFM.

With reference to the fourth possible implementation manner of the firstaspect, in a fifth possible implementation manner of the first aspect,the message sending module is configured to: send the query requestmessage to the VNFM, to send the query request message to a NFVorchestrator (NFVO) by using the VNFM and to send the query requestmessage to the second communications unit by using the NFVO.

With reference to the third possible implementation manner of the firstaspect, in a sixth possible implementation manner of the first aspect,the message sending module is configured to: send the query requestmessage to an operations support system (OSS)/business support system(BSS), to send the query request message to an NFVO by using the OSS/BSSand to send the query request message to the second communications unitby using the NFVO.

With reference to the sixth possible implementation manner of the firstaspect, in a seventh possible implementation manner of the first aspect,the message sending module is configured to: send the query requestmessage to the OSS/BSS, to send the query request message to the NFVO byusing the OSS/BSS, to send the query request message to a VNFM by usingthe NFVO, and to send the query request message to the secondcommunications unit by using the VNFM.

With reference to the first aspect to the seventh possibleimplementation manner of the first aspect, in an eighth possibleimplementation manner of the first aspect, the message sending unit isconfigured to: send the route and resource configuration request messageto the second communications unit, to request the second communicationsunit to perform the route and resource configuration.

With reference to the eighth possible implementation manner of the firstaspect, in a ninth possible implementation manner of the first aspect,the message sending unit is configured to: send the route and resourceconfiguration request message to the VNFM, to send the route andresource configuration request message to the second communications unitby using the VNFM.

With reference to the ninth possible implementation manner of the firstaspect, in a tenth possible implementation manner of the first aspect,the message sending unit is configured to: send the route and resourceconfiguration request message to the VNFM, to send the route andresource configuration request message to the NFVO by using the VNFM andto send the route and resource configuration request message to thesecond communications unit by using the NFVO.

With reference to the eighth possible implementation manner of the firstaspect, in an eleventh possible implementation manner of the firstaspect, the message sending unit is configured to: send the route andresource configuration request message to the OSS/BSS, to send the routeand resource configuration request message to the NFVO by using theOSS/BSS and to send the route and resource configuration request messageto the second communications unit by using the NFVO.

With reference to the eleventh possible implementation manner of thefirst aspect, in a twelfth possible implementation manner of the firstaspect, the message sending unit is configured to: send the route andresource configuration request message to the OSS/BSS, to send the routeand resource configuration request message to the NFVO by using theOSS/BSS, to send the route and resource configuration request message tothe VNFM by using the NFVO, and to send the route and resourceconfiguration request message to the second communications unit by usingthe VNFM.

With reference to the first aspect to the twelfth possibleimplementation manner of the first aspect, in a thirteenth possibleimplementation manner of the first aspect, the first communications unitfurther includes a receiving unit, where the receiving unit isconfigured to: if the route and resource configuration succeeds, receiveinformation indicating that the route and resource configurationsucceeds.

According to a second aspect, a second communications unit is provided,where the second communications unit includes a receiving unit and aconfiguration unit, where the receiving unit is configured to receive aroute and resource configuration request message, where the route andresource configuration request message carries information about aservice link through which a service route passes, to request toperform, according to the information about the service link, route andresource configuration for a VNF included in the service link, where theinformation about the service link is obtained according to a servicelink rule, the service link rule is used to indicate service processingthat needs to be performed, the information about the service link isused to indicate information about the VNF through which the serviceroute passes, and the VNF is configured for the service processing.Additionally, the configuration unit is configured to perform, accordingto the information about the service link received by the receiving unitand information about a physical resource of a network functionvirtualization infrastructure (NFVI), service route and resourceconfiguration for the VNF included in the service link.

With reference to the first aspect, in a first possible implementationmanner of the second aspect, the second communications unit furtherincludes: a query unit and a sending unit, where the receiving unit isfurther configured to: before receiving the route and resourceconfiguration request message, receive a query request message, wherethe query request message carries identification information of a VNFincluded in each VNF type in a type of the VNF through which the serviceroute passes, to request to query, according to the identificationinformation of the VNF, first information of the VNF included in eachVNF type, where the first information is used to indicate a networktopology, a node capability, and a status of the NFVI; the query unit isconfigured to: according to the query request message received by thereceiving unit, query the physical resource of the NFVI, and obtain thefirst information of the VNF included in each VNF type; and the sendingunit is configured to send the first information, obtained by the queryunit through query, of the VNF included in each VNF type, to generatethe information about the service link according to the firstinformation of the VNF included in each VNF type.

With reference to the second aspect or the first possible implementationmanner of the second aspect, in a second possible implementation mannerof the second aspect, the receiving unit is configured to: receive theroute and resource configuration request message sent by a VNFM.

With reference to the second aspect or the first possible implementationmanner of the second aspect, in a third possible implementation mannerof the second aspect, the receiving unit is configured to: receive theroute and resource configuration request message sent by a VNF OSS/BSS.

With reference to the second aspect to the third possible implementationmanner of the second aspect, in a fourth possible implementation mannerof the second aspect, the sending unit is further configured to: if theroute and resource configuration succeeds, send information indicatingthat the route and resource configuration succeeds.

According to a third aspect, an OSS/BSS is provided, where the OSS/BSSincludes: an obtaining unit and a sending unit, where the obtaining unitis configured to obtain information about a service link templatethrough which a service route passes, where the service link templateinformation is used to indicate a correspondence between a service linkidentifier and information about a service link; and the sending unit isconfigured to send the service link template information obtained by theobtaining unit to an NFV orchestrator NFVO, so that the NFVO requests,according to the service link template information, to perform route andresource configuration for a VNF included in a service link in theservice link template.

With reference to the third aspect, in a first possible implementationmanner of the third aspect, the OSS/BSS further includes a receivingunit, where the receiving unit is configured to receive informationindicating that the service link template information has been received.

With reference to the third aspect or the first possible implementationmanner of the third aspect, in a second possible implementation mannerof the third aspect, the receiving unit is further configured to: if theroute and resource configuration succeeds, receive informationindicating that the route and resource configuration succeeds.

According to a fourth aspect, a NFVO is provided, where the NFVOincludes: a receiving unit and a sending unit, where the receiving unitis configured to receive information about a service link templatethrough which a service route passes, where the service link templateinformation is used to indicate a correspondence between a service linkidentifier and information about a service link; and the sending unit isconfigured to send a route and resource configuration request message,where the route and resource configuration request message carries theservice link template information received by the receiving unit, torequest to perform, according to the service link template information,route and resource configuration for a VNF included in a service link inthe service link template.

With reference to the fourth aspect, in a first possible implementationmanner of the fourth aspect, the sending module is configured to: sendthe route and resource configuration request message to a secondcommunications unit, to request the second communications unit toperform, according to the service link template information, the routeand resource configuration for the VNF included in the service link inthe service link template.

With reference to the fourth aspect or the first possible implementationmanner of the fourth aspect, in a second possible implementation mannerof the fourth aspect, the sending unit is further configured to: afterthe receiving unit receives the information about the service linktemplate through which the service route passes, send informationindicating that the service link template information has been received.

With reference to the fourth aspect to the second possibleimplementation manner of the fourth aspect, in a third possibleimplementation manner of the fourth aspect, the receiving unit isfurther configured to: if the route and resource configuration succeeds,receive information indicating that the route and resource configurationsucceeds.

According to a fifth aspect, a second communications unit is provided,where the second communications unit includes: a receiving unit and aconfiguration unit, where the receiving unit is configured to receive aroute and resource configuration request message, where the route andresource configuration request message carries information about aservice link template through which a service route passes, to requestto perform, according to the service link template information, routeand resource configuration for a VNF included in a service link in theservice link template, where the service link template information isused to indicate a correspondence between a service link identifier andinformation about a service link; and the configuration unit isconfigured to perform, according to the service link templateinformation received by the receiving unit and information about aphysical resource of a NFVI, the route and resource configuration forthe VNF included in the service link in the service link template.

With reference to the fifth aspect, in a first possible implementationmanner of the fifth aspect, the receiving unit is configured to: receivethe route and resource configuration request message sent by an NFVorchestrator NFVO.

With reference to the first possible implementation manner of the fifthaspect, in a second possible implementation manner of the fifth aspect,the second communications unit further includes a sending unit, wherethe sending unit is configured to: if the route and resourceconfiguration succeeds, send information indicating that the route andresource configuration succeeds.

According to a sixth aspect, a method for service implementation in aNFV system is provided, where the method includes: obtaining, by a firstcommunications unit, a service link rule, where the service link rule isused to indicate service processing that needs to be performed;obtaining, according to the service link rule, information about aservice link through which a service route passes, where the informationabout the service link is used to indicate information about a VNFthrough which the service route passes, and the VNF is configured forthe service processing; and sending a route and resource configurationrequest message, where the route and resource configuration requestmessage carries the information about the service link, to request toperform, according to the information about the service link, route andresource configuration for the VNF included in the service link.

With reference to the sixth aspect, in a first possible implementationmanner of the sixth aspect, before the obtaining, according to theservice link rule, information about a service link through which aservice route passes, the method further includes: determining whetherthe service link rule includes the information about the service link;and the obtaining, according to the service link rule, information abouta service link through which a service route passes includes: if theservice link rule does not include the information about the servicelink, determining, according to the service link rule, a type of the VNFthrough which the service route passes and identification information ofa VNF included in each VNF type in the type of the VNF; sending a queryrequest message, where the query request message carries theidentification information of the VNF included in each VNF type, torequest to query, according to the identification information of theVNF, first information of the VNF included in each VNF type, where thefirst information is used to indicate a network topology, a nodecapability, and a status of a network function virtualizationinfrastructure (NFVI); receiving the first information of the VNFincluded in each VNF type; and generating the information about theservice link according to the first information of the VNF included ineach VNF type.

With reference to the first possible implementation manner of the sixthaspect, in a second possible implementation manner of the sixth aspect,the obtaining, according to the service link rule, information about aservice link through which a service route passes further includes: ifthe service link rule includes the information about the service link,obtaining the information about the service link included in the servicelink rule.

With reference to the first possible implementation manner of the sixthaspect or the second possible implementation manner of the sixth aspect,in a third possible implementation manner of the sixth aspect, thesending a query request message includes: sending the query requestmessage to a second communications unit, to request the secondcommunications unit to query, according to the identificationinformation of the VNF, the first information of the VNF included ineach VNF type.

With reference to the third possible implementation manner of the sixthaspect, in a fourth possible implementation manner of the sixth aspect,the sending the query request message to a second communications unitincludes: sending the query request message to a VNFM, to send the queryrequest message to the second communications unit by using the VNFM.

With reference to the fourth possible implementation manner of the sixthaspect, in a fifth possible implementation manner of the sixth aspect,the sending the query request message to a VNFM, to send the queryrequest message to the second communications unit by using the VNFMincludes: sending the query request message to the VNFM, to send thequery request message to an NFVO by using the VNFM and to send the queryrequest message to the second communications unit by using the NFVO.

With reference to the third possible implementation manner of the sixthaspect, in a sixth possible implementation manner of the sixth aspect,the sending the query request message to a second communications unitincludes: sending the query request message to an OSS/BSS, to send thequery request message to an NFVO by using the OSS/BSS and to send thequery request message to the second communications unit by using theNFVO.

With reference to the sixth possible implementation manner of the sixthaspect, in a seventh possible implementation manner of the sixth aspect,the sending the query request message to an OSS/BSS, to send the queryrequest message to an NFVO by using the OSS/BSS and to send the queryrequest message to the second communications unit by using the NFVOincludes: sending the query request message to the OSS/BSS, to send thequery request message to the NFVO by using the OSS/BSS, to send thequery request message to a VNFM by using the NFVO, and to send the queryrequest message to the second communications unit by using the VNFM.

With reference to the sixth aspect to the seventh possibleimplementation manner of the sixth aspect, in an eighth possibleimplementation manner of the sixth aspect, the sending a route andresource configuration request message includes: sending the route andresource configuration request message to the second communicationsunit, to request the second communications unit to perform the route andresource configuration.

With reference to the eighth possible implementation manner of the sixthaspect, in a ninth possible implementation manner of the sixth aspect,the sending the route and resource configuration request message to thesecond communications unit includes: sending the route and resourceconfiguration request message to the VNFM, to send the route andresource configuration request message to the second communications unitby using the VNFM.

With reference to the ninth possible implementation manner of the sixthaspect, in a tenth possible implementation manner of the sixth aspect,the sending the route and resource configuration request message to theVNFM, to send the route and resource configuration request message tothe second communications unit by using the VNFM includes: sending theroute and resource configuration request message to the VNFM, to sendthe route and resource configuration request message to the NFVO byusing the VNFM and to send the route and resource configuration requestmessage to the second communications unit by using the NFVO.

With reference to the eighth possible implementation manner of the sixthaspect, in an eleventh possible implementation manner of the sixthaspect, the sending the route and resource configuration request messageto the second communications unit includes: sending the route andresource configuration request message to the OSS/BSS, to send the routeand resource configuration request message to the NFVO by using theOSS/BSS and to send the route and resource configuration request messageto the second communications unit by using the NFVO.

With reference to the eleventh possible implementation manner of thesixth aspect, in a twelfth possible implementation manner of the sixthaspect, the sending the route and resource configuration request messageto the OSS/BSS, to send the route and resource configuration requestmessage to the NFVO by using the OSS/BSS and to send the route andresource configuration request message to the second communications unitby using the NFVO includes: sending the route and resource configurationrequest message to the OSS/BSS, to send the route and resourceconfiguration request message to the NFVO by using the OSS/BSS, to sendthe route and resource configuration request message to the VNFM byusing the NFVO, and to send the route and resource configuration requestmessage to the second communications unit by using the VNFM.

With reference to the sixth aspect to the twelfth possibleimplementation manner of the sixth aspect, in a thirteenth possibleimplementation manner of the sixth aspect, the method further includes:if the route and resource configuration succeeds, receiving informationindicating that the route and resource configuration succeeds.

According to a seventh aspect, a method for service implementation in aNFV system is provided, where the method includes: receiving, by asecond communications unit, a route and resource configuration requestmessage, where the route and resource configuration request messagecarries information about a service link through which a service routepasses, to request to perform, according to the information about theservice link, route and resource configuration for a VNF included in theservice link, where the information about the service link is obtainedaccording to a service link rule, the service link rule is used toindicate service processing that needs to be performed, the informationabout the service link is used to indicate information about the VNFthrough which the service route passes, and the VNF is configured forthe service processing; and performing, according to the informationabout the service link and information about a physical resource of aNFVI, service route and resource configuration for the VNF included inthe service link.

With reference to the seventh aspect, in a first possible implementationmanner of the seventh aspect, before the receiving a route and resourceconfiguration request message, the method further includes: receiving aquery request message, where the query request message carriesidentification information of a VNF included in each VNF type in a typeof the VNF through which the service route passes, to request to query,according to the identification information of the VNF, firstinformation of the VNF included in each VNF type, where the firstinformation is used to indicate a network topology, a node capability,and a status of the NFVI; according to the query request message,querying the physical resource of the NFVI, and obtaining the firstinformation of the VNF included in each VNF type; and sending the firstinformation of the VNF included in each VNF type, to generate theinformation about the service link according to the first information ofthe VNF included in each VNF type.

With reference to the seventh aspect or the first possibleimplementation manner of the seventh aspect, in a second possibleimplementation manner of the seventh aspect, the receiving a route andresource configuration request message includes: receiving the route andresource configuration request message sent by a VNFM.

With reference to the seventh aspect or the first possibleimplementation manner of the seventh aspect, in a third possibleimplementation manner of the seventh aspect, the receiving a route andresource configuration request message includes: receiving the route andresource configuration request message sent by a VNF OSS/BSS.

With reference to the seventh aspect to the third possibleimplementation manner of the seventh aspect, in a fourth possibleimplementation manner of the seventh aspect, the method furtherincludes: if the route and resource configuration succeeds, sendinginformation indicating that the route and resource configurationsucceeds.

According to an eighth aspect, a method for service implementation in aNFV system is provided, where the method includes: obtaining, by anOSS/BSS, information about a service link template through which aservice route passes, where the service link template information isused to indicate a correspondence between a service link identifier andinformation about a service link; and sending the service link templateinformation to an NFV orchestrator NFVO, so that the NFVO requests,according to the service link template information, to perform route andresource configuration for a VNF included in a service link in theservice link template.

With reference to the eighth aspect, in a first possible implementationmanner of the eighth aspect, the method further includes: receivinginformation indicating that the service link template information hasbeen received.

With reference to the eighth aspect or the first possible implementationmanner of the eighth aspect, in a second possible implementation mannerof the eighth aspect, the method further includes: if the route andresource configuration succeeds, receiving information indicating thatthe route and resource configuration succeeds.

According to a ninth aspect, a method for service implementation in aNFV system is provided, where the method includes: receiving, by an NFVorchestrator NFVO, information about a service link template throughwhich a service route passes, where the service link templateinformation is used to indicate a correspondence between a service linkidentifier and information about a service link; and sending a route andresource configuration request message, where the route and resourceconfiguration request message carries the service link templateinformation, to request to perform, according to the service linktemplate information, route and resource configuration for a VNFincluded in a service link in the service link template.

With reference to the ninth aspect, in a first possible implementationmanner of the ninth aspect, the sending a route and resourceconfiguration request message includes: sending the route and resourceconfiguration request message to a second communications unit, torequest the second communications unit to perform, according to theservice link template information, the route and resource configurationfor the VNF included in the service link in the service link template.

With reference to the ninth aspect or the first possible implementationmanner of the ninth aspect, in a second possible implementation mannerof the ninth aspect, after the receiving, by an NFVO, information abouta service link template through which a service route passes, the methodfurther includes: sending information indicating that the service linktemplate information has been received.

With reference to the ninth aspect to the second possible implementationmanner of the ninth aspect, in a third possible implementation manner ofthe ninth aspect, the method further includes: if the route and resourceconfiguration succeeds, receiving information indicating that the routeand resource configuration succeeds.

According to a tenth aspect, a method for service implementation in aNFV system is provided, where the method includes: receiving, by asecond communications unit, a route and resource configuration requestmessage, where the route and resource configuration request messagecarries information about a service link template through which aservice route passes, to request to perform, according to the servicelink template information, route and resource configuration for a VNFincluded in a service link in the service link template, where theservice link template information is used to indicate a correspondencebetween a service link identifier and information about a service link;and performing, according to the information about the service link andinformation about a physical resource of a NFVI, the route and resourceconfiguration for the VNF included in the service link in the servicelink template.

With reference to the tenth aspect, in a first possible implementationmanner of the tenth aspect, the receiving a route and resourceconfiguration request message includes: receiving the route and resourceconfiguration request message sent by an NFV orchestrator NFVO.

With reference to the tenth aspect or the first possible implementationmanner of the tenth aspect, in a second possible implementation mannerof the tenth aspect, the method further includes: if the route andresource configuration succeeds, sending information indicating that theroute and resource configuration succeeds.

According to an eleventh aspect, a first communications unit isprovided, where the first communications unit includes: a processor anda transmitter, where the processor is configured to obtain a servicelink rule, where the service link rule is used to indicate serviceprocessing that needs to be performed; the processor is furtherconfigured to obtain, according to the service link rule, informationabout a service link through which a service route passes, where theinformation about the service link is used to indicate information abouta VNF through which the service route passes, and the VNF is configuredfor the service processing; and the transmitter is configured to send aroute and resource configuration request message, where the route andresource configuration request message carries the information about theservice link obtained by the processor, to request to perform, accordingto the information about the service link, route and resourceconfiguration for the VNF included in the service link.

With reference to the eleventh aspect, in a first possibleimplementation manner of the eleventh aspect, the processor is furtherconfigured to: before obtaining, according to the service link rule, theinformation about the service link through which the service routepasses, determine whether the service link rule includes the informationabout the service link; and the processor being further configured toobtain, according to the service link rule, information about a servicelink through which a service route passes includes: if the service linkrule does not include the information about the service link,determining, according to the service link rule, a type of the VNFthrough which the service route passes and identification information ofa VNF included in each VNF type in the type of the VNF; sending a queryrequest message, where the query request message carries theidentification information of the VNF included in each VNF type, torequest to query, according to the identification information of theVNF, first information of the VNF included in each VNF type, where thefirst information is used to indicate a network topology, a nodecapability, and a status of a NFVI; receiving the first information ofthe VNF included in each VNF type; and generating the information aboutthe service link according to the first information of the VNF includedin each VNF type.

With reference to the first possible implementation manner of theeleventh aspect, in a second possible implementation manner of theeleventh aspect, the obtaining, by the processor according to theservice link rule, information about a service link through which aservice route passes further includes: if the service link rule includesthe information about the service link, obtaining the information aboutthe service link included in the service link rule.

With reference to the first possible implementation manner of theeleventh aspect or the second possible implementation manner of theeleventh aspect, in a third possible implementation manner of theeleventh aspect, the sending, by the processor, a query request messageincludes: sending the query request message to a second communicationsunit, to request the second communications unit to query, according tothe identification information of the VNF, the first information of theVNF included in each VNF type.

With reference to the third possible implementation manner of theeleventh aspect, in a fourth possible implementation manner of theeleventh aspect, the sending, by the processor, a query request messageincludes: sending the query request message to a VNFM, to send the queryrequest message to the second communications unit by using the VNFM.

With reference to the fourth possible implementation manner of theeleventh aspect, in a fifth possible implementation manner of theeleventh aspect, the sending, by the processor, a query request messageincludes: sending the query request message to the VNFM, to send thequery request message to a NFVO by using the VNFM and to send the queryrequest message to the second communications unit by using the NFVO.

With reference to the third possible implementation manner of theeleventh aspect, in a sixth possible implementation manner of theeleventh aspect, the sending, by the processor, a query request messageincludes: sending the query request message to an OSS/BSS, to send thequery request message to an NFVO by using the OSS/BSS and to send thequery request message to the second communications unit by using theNFVO.

With reference to the sixth possible implementation manner of theeleventh aspect, in a seventh possible implementation manner of theeleventh aspect, the sending, by the processor, a query request messageincludes: sending the query request message to the OSS/BSS, to send thequery request message to the NFVO by using the OSS/BSS, to send thequery request message to a VNFM by using the NFVO, and to send the queryrequest message to the second communications unit by using the VNFM.

With reference to the eleventh aspect to the seventh possibleimplementation manner of the eleventh aspect, in an eighth possibleimplementation manner of the eleventh aspect, the transmitter isconfigured to: send the route and resource configuration request messageto the second communications unit, to request the second communicationsunit to perform the route and resource configuration.

With reference to the eighth possible implementation manner of theeleventh aspect, in a ninth possible implementation manner of theeleventh aspect, the transmitter is configured to: send the route andresource configuration request message to the VNFM, to send the routeand resource configuration request message to the second communicationsunit by using the VNFM.

With reference to the ninth possible implementation manner of theeleventh aspect, in a tenth possible implementation manner of theeleventh aspect, the transmitter is configured to: send the route andresource configuration request message to the VNFM, to send the routeand resource configuration request message to the NFVO by using the VNFMand to send the route and resource configuration request message to thesecond communications unit by using the NFVO.

With reference to the eighth possible implementation manner of theeleventh aspect, in an eleventh possible implementation manner of theeleventh aspect, the transmitter is configured to: send the route andresource configuration request message to the OSS/BSS, to send the routeand resource configuration request message to the NFVO by using theOSS/BSS and to send the route and resource configuration request messageto the second communications unit by using the NFVO.

With reference to the eleventh possible implementation manner of theeleventh aspect, in a twelfth possible implementation manner of theeleventh aspect, the transmitter is configured to: send the route andresource configuration request message to the OSS/BSS, to send the routeand resource configuration request message to the NFVO by using theOSS/BSS, to send the route and resource configuration request message tothe VNFM by using the NFVO, and to send the route and resourceconfiguration request message to the second communications unit by usingthe VNFM.

With reference to the eleventh aspect to the twelfth possibleimplementation manner of the eleventh aspect, in a thirteenth possibleimplementation manner of the eleventh aspect, the first communicationsunit further includes a receiver, where the receiver is configured to:if the route and resource configuration succeeds, receive informationindicating that the route and resource configuration succeeds.

According to a twelfth aspect, a second communications unit is provided,where the second communications unit includes: a receiver and aprocessor, where the receiver is configured to receive a route andresource configuration request message, where the route and resourceconfiguration request message carries information about a service linkthrough which a service route passes, to request to perform, accordingto the information about the service link, route and resourceconfiguration for a VNF included in the service link, where theinformation about the service link is obtained according to a servicelink rule, the service link rule is used to indicate service processingthat needs to be performed, the information about the service link isused to indicate information about the VNF through which the serviceroute passes, and the VNF is configured for the service processing; andthe processor is configured to perform, according to the informationabout the service link received by the receiver and information about aphysical resource of a NFVI, service route and resource configurationfor the VNF included in the service link.

With reference to the eleventh aspect, in a first possibleimplementation manner of the twelfth aspect, the second communicationsunit further includes: a transmitter, where the receiver is furtherconfigured to: before receiving the route and resource configurationrequest message, receive a query request message, where the queryrequest message carries identification information of a VNF included ineach VNF type in a type of the VNF through which the service routepasses, to request to query, according to the identification informationof the VNF, first information of the VNF included in each VNF type,where the first information is used to indicate a network topology, anode capability, and a status of the NFVI; the processor is furtherconfigured to: according to the query request message received by thereceiver, query the physical resource of the NFVI, and obtain the firstinformation of the VNF included in each VNF type; and the transmitter isconfigured to send the first information, obtained by the processorthrough query, of the VNF included in each VNF type, to generate theinformation about the service link according to the first information ofthe VNF included in each VNF type.

With reference to the twelfth aspect or the first possibleimplementation manner of the twelfth aspect, in a second possibleimplementation manner of the twelfth aspect, the receiver is configuredto: receive the route and resource configuration request message sent bya VNFM.

With reference to the twelfth aspect or the first possibleimplementation manner of the twelfth aspect, in a third possibleimplementation manner of the twelfth aspect, the receiver is configuredto: receive the route and resource configuration request message sent bya VNF OSS/BSS.

With reference to the twelfth aspect to the third possibleimplementation manner of the twelfth aspect, in a fourth possibleimplementation manner of the twelfth aspect, the transmitter is furtherconfigured to: if the route and resource configuration succeeds, sendinformation indicating that the route and resource configurationsucceeds.

According to a thirteenth aspect, OSS/BSS is provided, where the OSS/BSSincludes: a processor and a transmitter, where the processor isconfigured to obtain information about a service link template throughwhich a service route passes, where the service link templateinformation is used to indicate a correspondence between a service linkidentifier and information about a service link; and the transmitter isconfigured to send the service link template information obtained by theprocessor to an NFV orchestrator NFVO, so that the NFVO requests,according to the service link template information, to perform route andresource configuration for VNF included in a service link in the servicelink template.

With reference to the thirteenth aspect, in a first possibleimplementation manner of the thirteenth aspect, the OSS/BSS furtherincludes a receiver, where the receiver is configured to receiveinformation indicating that the service link template information hasbeen received.

With reference to the thirteenth aspect or the first possibleimplementation manner of the thirteenth aspect, in a second possibleimplementation manner of the thirteenth aspect, the receiver is furtherconfigured to: if the route and resource configuration succeeds, receiveinformation indicating that the route and resource configurationsucceeds.

According to a fourteenth aspect, a NFVO is provided, where the NFVOincludes: a receiver and a transmitter, where the receiver is configuredto receive information about a service link template through which aservice route passes, where the service link template information isused to indicate a correspondence between a service link identifier andinformation about a service link; and the transmitter is configured tosend a route and resource configuration request message, where the routeand resource configuration request message carries the service linktemplate information received by the receiver, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate.

With reference to the fourteenth aspect, in a first possibleimplementation manner of the fourteenth aspect, the transmitter isconfigured to: send the route and resource configuration request messageto a second communications unit, to request the second communicationsunit to perform, according to the service link template information, theroute and resource configuration for the VNF included in the servicelink in the service link template.

With reference to the fourteenth aspect or the first possibleimplementation manner of the fourteenth aspect, in a second possibleimplementation manner of the fourteenth aspect, the transmitter isfurther configured to: after the receiver receives the information aboutthe service link template through which the service route passes, sendinformation indicating that the service link template information hasbeen received.

With reference to the fourteenth aspect to the second possibleimplementation manner of the fourteenth aspect, in a third possibleimplementation manner of the fourteenth aspect, the receiver is furtherconfigured to: if the route and resource configuration succeeds, receiveinformation indicating that the route and resource configurationsucceeds.

According to a fifteenth aspect, a second communications unit isprovided, where the second communications unit includes: a receiver anda processor, where the receiver is configured to receive a route andresource configuration request message, where the route and resourceconfiguration request message carries information about a service linktemplate through which a service route passes, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate, where the service link template information is used toindicate a correspondence between a service link identifier andinformation about a service link; and the processor is configured toperform, according to the service link template information received bythe receiver and information about a physical resource of a NFVI, theroute and resource configuration for the VNF included in the servicelink in the service link template.

With reference to the fifteenth aspect, in a first possibleimplementation manner of the fifteenth aspect, the receiver isconfigured to: receive the route and resource configuration requestmessage sent by an NFV orchestrator NFVO.

With reference to the first possible implementation manner of thefifteenth aspect, in a second possible implementation manner of thefifteenth aspect, the second communications unit further includes atransmitter, where the transmitter is configured to: if the route andresource configuration succeeds, send information indicating that theroute and resource configuration succeeds.

The embodiments provide a method for service implementation in an NFVsystem and a communications unit. Based on the foregoing technicalsolutions, after obtaining a service link rule, a first communicationsunit can obtain, according to the service link rule, information about aservice link through which a service route passes, and then send a routeand configuration request message that carries the information about theservice link, to request to perform route and resource configurationaccording to the information about the service link, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of an NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link; or an OSS/BSS can obtaininformation about a service link template through which a service routepasses, and then send the service link template information to an NFVO,and the NFVO requests route and resource configuration according to theservice link template information, implementing a function of obtainingupper-layer information about a service link and guiding route andresource configuration of an NFVI by using the upper-layer informationabout a service link, and implementing establishment of an NFV networkservice link.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the embodiments more clearly, thefollowing briefly describes the accompanying drawings required fordescribing the embodiments or the prior art. Apparently, theaccompanying drawings in the following description show merely someembodiments, and a person of ordinary skill in the art may still deriveother drawings from these accompanying drawings without creativeefforts.

FIG. 1 is a schematic diagram of a network function virtualization (NFV)architecture according to an embodiment;

FIG. 2 is a schematic diagram of a service link of a network serviceaccording to an embodiment;

FIG. 3 shows a method for service implementation in an NFV systemaccording to an embodiment;

FIG. 4 is a schematic diagram of a scenario of a method for serviceimplementation in an NFV system according to an embodiment;

FIG. 5 shows a method for service implementation in an NFV systemaccording to an embodiment;

FIG. 6 is a schematic diagram of service management of an NFV systemaccording to an embodiment;

FIG. 7 is a schematic diagram of service management of another NFVsystem according to an embodiment;

FIG. 8 is a schematic diagram of a correspondence between a virtualizednetwork function (VNF) and a routing device of an NFV interface (NFVI)according to an embodiment;

FIG. 9 shows a method for service implementation in an NFV systemaccording to an embodiment;

FIG. 10 shows another method for service implementation in an NFV systemaccording to an embodiment;

FIG. 11 shows still another method for service implementation in an NFVsystem according to an embodiment;

FIG. 12 shows still another method for service implementation in an NFVsystem according to an embodiment;

FIG. 13 shows still another method for service implementation in an NFVsystem according to an embodiment;

FIG. 14A and FIG. 14B show still another method for serviceimplementation in an NFV system according to an embodiment;

FIG. 15 shows still another method for service implementation in an NFVsystem according to an embodiment;

FIG. 16A and FIG. 16B show still another method for serviceimplementation in an NFV system according to an embodiment;

FIG. 17 is a schematic structural diagram of a first communications unitaccording to an embodiment;

FIG. 18 is a schematic structural diagram of another firstcommunications unit according to an embodiment;

FIG. 19 is a schematic structural diagram of still another firstcommunications unit according to an embodiment;

FIG. 20 is a schematic structural diagram of still another firstcommunications unit according to an embodiment;

FIG. 21 is a schematic structural diagram of a second communicationsunit according to an embodiment;

FIG. 22 is a schematic structural diagram of another secondcommunications unit according to an embodiment;

FIG. 23 is a schematic structural diagram of an operations supportsystem/business support system (OSS/BSS) according to an embodiment;

FIG. 24 is a schematic structural diagram of another OSS/BSS accordingto an embodiment;

FIG. 25 is a schematic structural diagram of an NFVO according to anembodiment;

FIG. 26 is a schematic structural diagram of a second communicationsunit according to an embodiment;

FIG. 27 is a schematic structural diagram of another secondcommunications unit according to an embodiment;

FIG. 28 is a schematic structural diagram of a first communications unitaccording to an embodiment;

FIG. 29 is a schematic structural diagram of another firstcommunications unit according to an embodiment;

FIG. 30 is a schematic structural diagram of a second communicationsunit according to an embodiment;

FIG. 31 is a schematic structural diagram of another secondcommunications unit according to an embodiment;

FIG. 32 is a schematic structural diagram of an OSS/BSS according to anembodiment;

FIG. 33 is a schematic structural diagram of another OSS/BSS accordingto an embodiment;

FIG. 34 is a schematic structural diagram of an NFVO according to anembodiment;

FIG. 35 is a schematic structural diagram of a second communicationsunit according to an embodiment; and

FIG. 36 is a schematic structural diagram of another secondcommunications unit according to an embodiment.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

For ease of understanding, a network function virtualization (NFV)architecture is first described. As shown in FIG. 1, functional units inthe architecture include:

(1) Virtualized network function (VNF) unit: Correspond to a physicalnetwork function (PNF) in a conventional non-virtualized network. Forexample, the VNF unit may be a virtualized evolved packet core (EPC)node, a mobility management entity (MME), a serving gateway (SGW), apacket data network-gateway (PGW), or the like). The VNF and the PNFhave a same functional behavior and external interface.

(2) Element management system (EMS) unit: Perform a fault management,configuration management, accounting management, performance management,security management (Fault Management, Configuration Management,Accounting Management, Performance Management, Security Management,(FCAPS)) function for the VNF.

(3) NFV infrastructure (NFVI) unit: The NFVI includes a hardwareresource, a virtual resource, and a virtualization layer.

The virtual resource refers to a resource that is simulated by usingsoftware and that has a hardware system function. The virtualizationlayer refers to a virtual host platform having an advanced resourcemanagement function.

Generally, a combination of the virtualization layer and the hardwareresource is an entity that can provide a required virtual resource tothe VNF.

(4) Virtualized infrastructure management (VIM) unit: Include avirtualized entity configured to control and manage computation andstorage of a virtual network resource and the virtual network resource.

(5) NFV orchestrator (NFVO): Responsible for orchestrating and managingan NFV resource (including NFVI and VNF resources), and implementing anNFV service topology on the NFVI.

(6) VNF manager (VNFM) unit: Responsible for life cycle management of aVNF instance.

(7) Operations support system/business support system (OSS/BSS): Referto an integrated and resource information sharing support system of atelecommunications operator, and mainly include parts such as networkmanagement, system management, charging, business, account, and customerservice.

The NFVO, the VNFM, and the VIM together form an NFV management andnetwork orchestration (NFV Management and network Orchestration, (NFVMANO)) architecture.

A configuration file in the NFV architecture shown in FIG. 1 includes:service, VNF, and infrastructure description, providing VNF connectionrelated information, service related information, and VNF and NFVIinformation models.

Interfaces in the NFV architecture shown in FIG. 1 include.

(1) VI-Ha interface between the virtualization layer and the hardwareresource: The virtualization layer may request, by using the interface,the hardware resource to collect related hardware resource statusinformation.

(2) Vn-Nf interface between the VNF and the NFVI: Describe an executionenvironment provided by the NFVI to the VNF.

(3) Or-Vnfm interface between the NFVO and the VNFM: An internalinterface in the NFV MANO.

Function 1: The VNFM sends a resource related request to the NFVO, forexample, resource authorization, authentication, reservation, andallocation, for VNF life cycle management.

Function 2: The NFVO sends configuration information to the VNFM, sothat the VNF can be appropriately configured according to a VNFforwarding graph.

Function 3: Collect VNF status information for VNF life cyclemanagement.

(4) Vi-Vnfm interface between the VIM and the VNFM: An internalinterface in the NFV MANO.

Function 1: The VNFM sends a resource allocation request.

Function 2: Configure a virtual hardware resource and a route andexchange status information (for example, events).

(5) Or-Vi interface between the NFVO and the VIM: An internal interfacein the NFV MANO.

Function 1: The NFVO sends a resource reservation request.

Function 2: The NFVO sends a resource allocation request.

Function 3: Configure a virtual hardware resource and a route andexchange status information (for example, events).

(6) Nf-Vi interface between the NFVI and the VIM.

Function 1: Allocate a particular resource according to a resourceallocation request.

Function 2: Forward virtual resource status information.

Function 3: Configure a virtual hardware resource and a route andexchange status information (for example, events).

(7) Os-Ma interface between the OSS/BSS and the NFVO.

Function 1: Request service life cycle management.

Function 2: Request VNF life cycle management.

Function 3: Forward NFV related status information.

Function 4: Exchange policy management information.

Function 5: Exchange data analysis information.

Function 6: Forward NFV related charging and use records.

Function 7: Exchange capacity and stock information.

(8) Ve-Vnfm interface between the VNF/EMS and the VNFM.

Function 1: Request VNF life cycle management.

Function 2: Exchange configuration information.

Exchange status information required by service life cycle management.

(9) Se-Ma interface between the service, VNF, and infrastructuredescription and the NFV MANO: The interface is configured to retrieveVNF forwarding graph related information, service related information,VNF related information, and NFVI information model related information,and provide the information to the NFV MANO for use.

Next, a schematic diagram of a service link of a network service isprovided herein, as shown in FIG. 2. The service link includes twoendpoints (endpoint A and endpoint B), three VNFs (VNF1, VNF2, andVNF3), and three infrastructure networks (infrastructure network 1,infrastructure network 2, and infrastructure network 3), whereinfrastructure network 1 provides a link connection between endpoint Aand VNF1, infrastructure network 3 provides a link connection betweenVNF3 and endpoint B, infrastructure network 2 provides a link connectionbetween VNF1, VNF2, and VNF3, and VNF1, VNF2, and VNF3 are strung byusing a logical link provided by infrastructure network 2 and form anintegrated network function, that is, a service link for implementing aparticular function. In FIG. 2, a dashed line represents a logicalconnection, and a solid line represents a physical connection.

The following describes the technical solutions in the embodiments withreference to the accompanying drawings in the embodiments. Apparently,the described embodiments are merely some but not all of theembodiments. All other embodiments obtained by a person of ordinaryskill in the art based on the embodiments without creative efforts shallfall within the protection scope.

Embodiment 1

This embodiment provides a method for service implementation in an NFVsystem. As shown in FIG. 3, the method includes:

301: A first communications unit obtains a service link rule, where theservice link rule is used to indicate service processing that needs tobe performed.

The first communications unit that executes this embodiment may be aservice link controller, or may be a network node such as a PGW, apolicy and charging rules function entity (PCRF), a traffic detectionentity (TDF), or a traffic classifier, which is not limited in thisembodiment. The network node such as the PGW, the PCRF, the TDF, or thetraffic classifier may be a VNF unit, or may be a PNF unit, which is notlimited in this embodiment.

The service link controller is a controller configured to control aservice link. The service link controller is essentially asoftware-defined networking (SDN) controller. The SDN controllerimplements lower-layer device routing and data forwarding control byusing the OpenFlow protocol. A method for lower-layer device routing anddata forwarding control belongs to an existing technical solution.Details are not described herein.

It should be noted that, the service link controller may be a gigabitinternet (GI) local area network (LAN) controller, configured to controla service link of a GI LAN network. The GI LAN refers to a network froma wireless GI interface to the Internet, and includes different servicefunctions (SF). One service link includes multiple SFs, one service linkcorresponds to one service package, and one service package may includemultiple service links.

Certainly, the service link controller may be a service link controllerthat controls another network, which is not limited in this embodiment.

In this embodiment, the service link rule is used to indicate theservice processing that needs to be performed, and may include: aservice route policy, for example, video optimization.

It should be noted that, the service route policy is generallyrepresented by using a service route policy table, and the firstcommunications unit may determine the service route policy by queryingthe service route policy table.

Exemplarily, the service route policy table may be shown in FIG. 1:

TABLE 1 Transmission control protocol (Transmission Control Protocol,TCP) proxy (TCP proxy)−>video cache Video service (Video Cache)−>networkaddress translation acceleration (Network Address Translation, NAT)Browser service TCP proxy→Cache acceleration . . . . . .

Alternatively, the service link rule may further include: a logical unitthrough which a service route passes, for example, types of VNFs throughwhich video optimization needs to pass: TCP proxy->Video Cache->NAT; orinformation about a service link, for example, VNF7->VNF2->VNF3.

The service link rule is not limited in this embodiment.

302: The first communications unit obtains, according to the servicelink rule, information about a service link through which a serviceroute passes.

The information about the service link is used to indicate informationabout a VNF through which a service route passes, and the VNF isconfigured for the service processing.

As described in step 301, the service link rule may directly includeinformation about a service link, or may not include information about aservice link. Therefore, before the obtaining, by the firstcommunications unit according to the service link rule, informationabout a service link through which a service route passes, the methodmay further include: determining whether the service link rule includesthe information about the service link.

If the service link rule includes the information about the servicelink, the first communications unit may directly obtain the informationabout the service link included in the service link rule.

If the service link rule does not include the information about theservice link, the first communications unit may obtain the informationabout the service link in the following manner: determining, accordingto the service link rule, a type of the VNF through which the serviceroute passes and identification information of a VNF included in eachVNF type in the type of the VNF; sending a query request message, wherethe query request message carries the identification information of theVNF included in each VNF type, to request to query, according to theidentification information of the VNF, first information of the VNFincluded in each VNF type, where the first information is used toindicate a network topology, a node capability, and a status of an NFVI;receiving the first information of the VNF included in each VNF type;and generating the information about the service link according to thefirst information of the VNF included in each VNF type.

It should be noted that, in this embodiment, the information about theservice link may be a service link indicated by VNF7->VNF2->VNF3, or maybe information that represents the service link, for example, theinformation about the service link may include information about theVNFs forming the service link, or may include a service streamidentifier, which is not limited in this embodiment.

It should be noted that, in this embodiment, as described in step 301,the first communications unit may be a VNF unit, or may be a PNF unit.

When the first communications unit is a VNF unit, the firstcommunications unit may directly send the query request message to aVNFM, to send the query request message to a second communications unitby using the VNFM; or may directly send the query request message to anOSS/BSS, to send the query request message to a second communicationsunit by using the OSS/BSS, which is not limited in this embodiment of.

When the first communications unit is a PNF unit, the firstcommunications unit can only directly send the query request message toan OSS/BSS, to send the query request message to a second communicationsunit by using the OSS/BSS, and cannot directly send the query requestmessage to a VNFM.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not described herein.

Certainly, there may be another method of obtaining, according to theservice link rule, information about a service link through which aservice route passes, which is not limited in this embodiment.

It should be noted that, when the service link rule includes theinformation about the service link, the first communications unit mayalso query, by using the second communications unit, first informationof the VNF included in the service link, to determine whether a state ofthe VNF included in the service link is abnormal. When the secondcommunications unit obtains through query that a state of a VNF includedin the service link is abnormal (for example, resource load exceeds apreset threshold), the second communications unit feeds back abnormalityinformation to the first communications unit in time, so that the firstcommunications unit feeds back the abnormality information to an entitythat sends the service link rule, and the entity that sends the servicelink rule then performs corresponding processing according to acorresponding policy, for example, re-sends information about a servicelink. Whether the first information of the VNF included in the servicelink needs to be queried by using the second communications unit whenthe service link rule includes the information about the service link isnot limited in this embodiment.

303: The first communications unit sends a route and resourceconfiguration request message, where the route and resourceconfiguration request message carries the information about the servicelink, to request to perform, according to the information about theservice link, route and resource configuration for a VNF included in theservice link.

As described in step 301, the first communications unit may be a VNFunit, or may be a PNF unit.

When the first communications unit is a VNF unit, the firstcommunications unit may directly send the route and resourceconfiguration request message to the VNFM, to send the route andresource configuration request message to the second communications unitby using the VNFM; or may directly send the route and resourceconfiguration request message to the OSS/BSS, to send the route andresource configuration request message to the second communications unitby using the OSS/BSS, which is not limited in this embodiment.

When the first communications unit is a PNF unit, the firstcommunications unit can only directly send the route and resourceconfiguration request message to the OSS/BSS, to send the route andresource configuration request message to the second communications unitby using the OSS/BSS, and cannot directly send the query request messageto the VNFM.

As described above, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment.

Certainly, if the route and resource configuration succeeds, the firstcommunications unit may further receive information indicating that theroute and resource configuration succeeds, which is not limited in thisembodiment.

In conclusion, exemplarily, it is assumed that the first communicationsunit that executes this embodiment is a service link controller, and aschematic diagram of a scenario of a method for service implementationin an NFV system is provided herein, as shown in FIG. 4, including: aPCRF, a PGW, a service link controller, an NFV system, and a networkthat can be supported, where the NFV system includes multiple VNF types,for example, video optimization, content filtering, and browseroptimization, each VNF type includes one or more VNFs; a network thatcan be supported is a 2rd Generation (2G) network, or a Universal MobileTelecommunications System (UMTS) network, or a Long Term Evolution (LTE)network.

In FIG. 4, a 3rd Generation Partnership Project (3rd GenerationPartnership Project, 3GPP) network element such as the PCRF serves as aservice link rule decision entity. After deciding a service link ruleaccording to user information, service information, and networkinformation, the PCRF notifies the service link controller, so that theservice link controller obtains the service link rule, where informationexchange and service link rule transfer are performed between theservice link controller and a wireless network node (for example, thePCRF or the PGW) by using the Diameter protocol.

The service link controller functions to obtain service link rule, andobtain, according to the service link rule, information about a servicelink through which a service route passes. In a possible implementationmanner, if the service link rule includes the information about theservice link, the service link controller may directly obtain theinformation about the service link included in the service link rule. Ifthe service link rule does not include the information about the servicelink, the service link controller instructs an NFV MANO to queryinformation such as the network topology of the NFVI and a resourcestatus, and generates the information about the service link accordingto the information such as the network topology of the NFVI and theresource status. After obtaining the information about the service link,the service link controller may instruct a VIM or an NFVI controller toperform route and resource configuration. The service link controllerserves as a VNF, and information exchange may be performed between theVNF and a VNFM by using the RESTful protocol.

Based on the method for service implementation in an NFV system providedin this embodiment, after obtaining a service link rule, a firstcommunications unit can obtain, according to the service link rule,information about a service link through which a service route passes,and then send a route and configuration request message that carries theinformation about the service link, to request to perform, according tothe information about the service link, route and resource configurationfor a VNF included in the service link, implementing a function ofobtaining upper-layer information about a service link and guiding routeand resource configuration of an NFVI by using the upper-layerinformation about a service link, and implementing establishment of anNFV network service link.

Embodiment 2

This embodiment provides a method for service implementation in an NFVsystem. As shown in FIG. 5, the method includes.

501: A second communications unit receives a route and resourceconfiguration request message, where the route and resourceconfiguration request message carries information about a service linkthrough which a service route passes, to request to perform, accordingto the information about the service link, route and resourceconfiguration for a VNF included in the service link.

The information about the service link is obtained according to aservice link rule, the service link rule is used to indicate serviceprocessing that needs to be performed, the information about the servicelink is used to indicate information about the VNF through which theservice route passes, and the VNF is configured for the serviceprocessing.

The second communications unit that executes this embodiment may be aVIM, or may be an NFVI controller, which is not limited in thisembodiment. The NFVI controller is similar to a service link controller,and essentially is also an SDN controller, the service link controllercontrols logic and routing of a VNF at a VNF layer, and the NFVIcontroller controls connection and routing of a physical resource of anNFVI. The NFVI controller may be deployed in a VIM or the NFVI, or maybe deployed independently, which is not limited in this embodiment.

It should be noted that, if there is an NFVI controller, because theNFVI controller may be deployed in a VIM, or may be deployedindependently, in this embodiment, in a case in which there is an NFVIcontroller and the NFVI controller is deployed in a VIM, it isconsidered that the second communications unit is the VIM; in a case inwhich there is an NFVI controller and the NFVI controller is deployed inthe NFVI or deployed independently, it may be considered that the secondcommunications unit is the NFVI controller; and if there is no NFVIcontroller, the second communications unit that executes this embodimentis a VIM.

Exemplarily, assuming that there is no NFVI controller, a schematicdiagram of service management of an NFV system that is shown in FIG. 6may be obtained, where the right side shows an NFV MANO architecture,and details are not repeated herein. The service link controllercontrols the logic and routing of the VNF at the VNF layer, the VIMmanages the connection and routing of the physical resource of the NFVI,and a virtual machine (Virtual Machine, VM) is configured to carry avirtual resource.

Exemplarily, assuming that there is an NFVI controller, a schematicdiagram of service management of an NFV system that is shown in FIG. 7may be obtained, where the right side shows an NFV MANO architecture,and details are not repeated herein. A service link controller controlslogic and routing of a VNF at a VNF layer, the NFVI controller managesconnection and routing of a physical resource of the NFVI, and a VM isconfigured to carry a virtual resource.

In this embodiment, the route and resource configuration request messagereceived by the second communications unit may be sent by a VNFM, or maybe sent by an OSS/BSS, which is not limited in this embodiment.

502: The second communications unit performs, according to theinformation about the service link and information about a physicalresource of an NFVI, the route and resource configuration for the VNFincluded in the service link.

In this embodiment, after receiving the route and resource configurationrequest message, the second communications unit may perform, accordingto the carried information about a service link and the informationabout the physical resource of the NFVI by using the following method,the route and resource configuration for the VNF included in the servicelink:

After obtaining the information about the service link, the secondcommunications unit separately determines, according to the carriedinformation about a service link and the information about the physicalresource of the NFVI, a routing device of the NFVI that corresponds tothe VNF included in the service link, and then separately sends aservice route information table to the routing device of the NFVI thatcorresponds to the VNF, and the routing device of the NFVI forwards acorresponding service stream according to the service route informationtable.

Exemplarily, assuming that the information about the service link is:VNF7->VNF2->VNF3, a service route information table shown in a case 1 ora case 2 may be sent to a routing device corresponding to VNF7.

Case 1:

service link identifier: VNF7->VNF2->VNF3;

VNF7 interface: interface 1; and

VNF2 interface: interface 2.

Case 2:

service link identifier: VNF7->VNF2;

VNF7 interface: interface 1; and

VNF2 interface: interface 2.

The service link identifier in the case 1 includes information about anentire service link, and the service link identifier in the case 2includes information only about a next hop.

Subsequently, the routing device of VNF7 forwards a correspondingservice stream according to a delivered service route information table.For example, according to the service route information tables providedin the two cases, a service stream is output from an output interface 1of the routing device of VNF7, and input from an input interface 2 of arouting device of VNF2.

It should be noted that, a correspondence shown in FIG. 8 exists betweenVNFs managed by the first communications unit and routing devices of theNFVI, that is, in hardware resources of the NFVI, the VNFs managed bythe first communications unit all have routing devices corresponding tothe VNFs.

It should be noted that, in this embodiment, the information about theservice link carried in the resource and configuration request messagemay be directly included in the service link rule obtained by the firstcommunications unit, or may be obtained after information about aphysical resource managed by the second communications unit is queriedaccording to the service link rule obtained by the first communicationsunit. Therefore, the method for service implementation in an NFV systemprovided in this embodiment may further include: receiving a queryrequest message, where the query request message carries identificationinformation of a VNF included in each VNF type in a type of the VNFthrough which the service route passes, to request to query, accordingto the identification information of the VNF, first information of theVNF included in each VNF type, where the first information is used toindicate a network topology, a node capability, and a status of theNFVI; according to the query request message, querying the physicalresource of the NFVI, and obtaining the first information of the VNFincluded in each VNF type; and sending the first information of the VNFincluded in each VNF type, to generate the information about the servicelink according to the first information of the VNF included in each VNFtype.

The query request message received by the second communications unit maybe sent by the VNFM, or may be sent by the OSS/BSS, which is not limitedin this embodiment.

Certainly, if the route and resource configuration succeeds, the secondcommunications unit may further send information indicating that theroute and resource configuration succeeds, which is not limited in thisembodiment.

Based on the method for service implementation in an NFV system providedin this embodiment, a second communications unit can receive a route andresource configuration request message, where the route and resourceconfiguration request message carries information about a service linkthrough which a service route passes, to request to perform, accordingto the information about the service link, route and resourceconfiguration for a VNF included in the service link; and then perform,according to the information about the service link and informationabout a physical resource of an NFVI, service route and resourceconfiguration for the VNF included in the service link, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of the NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 3

This embodiment provides a method for service implementation in an NFVsystem. As shown in FIG. 9, the method includes.

901: An OSS/BSS obtains information about a service link templatethrough which a service route passes.

The service link template information is used to indicate acorrespondence between a service link identifier and information about aservice link.

In this embodiment, the OSS/BSS may generate and maintain informationabout service link templates through which service routes of allservices pass, and in a process of service implementation in an NFVsystem, the OSS/BSS may first obtain the service link templateinformation, where the service link template information is used toindicate a correspondence between a service link identifier andinformation about a service link.

In this embodiment, the service link template information may includeinformation such as a service link identifier and a sequence of VNFscorresponding to a service link, which is not limited in thisembodiment.

Exemplarily, the service link template information may be shown in Table2:

TABLE 2 Service link identifier Service link 1 VNF₇−>VNF₂−>VNF₃−>VNF6 2VNF₁−>VNF₇−>VNF₃ 3 VNF 6−>VNF₄>VNF₂−>VNF₅ . . . . . .

It should be noted that, the service link template may be stored in anetwork service description (NSD) or a VNF description (VNFD), or may beindependent of an NSD and a VNFD, which is not limited in thisembodiment.

902: The OSS/BSS sends the service link template information to an NFVO,so that the NFVO requests, according to the service link templateinformation, to perform route and resource configuration for a VNFincluded in a service link in the service link template.

In this embodiment, after obtaining the service link templateinformation, the OSS/BSS may send the service link template informationto an NFVO, and the NFVO requests, according to the service linktemplate information, to perform route and resource configuration for aVNF included in a service link in the service link template.

Certainly, after sending the service link template information to theNFVO, the OSS/BSS may further receive information indicating that theservice link template information has been received, which is notlimited in this embodiment.

In addition, after the OSS/BSS sends the service link templateinformation to the NFVO, if the route and resource configurationsucceeds, the OSS/BSS may further receive information indicating thatthe route and resource configuration succeeds, which is not limited inthis embodiment.

Based on the method for service implementation in an NFV system providedin this embodiment, an OSS/BSS can obtain information about a servicelink template through which a service route passes, where the servicelink template information is used to indicate a correspondence between aservice link identifier and information about a service link; and thensend the service link template information to an NFVO, so that the NFVOrequests, according to the service link template information, to performroute and resource configuration for a VNF included in a service link inthe service link template, implementing a function of obtainingupper-layer information about a service link and guiding route andresource configuration of an NFVI by using the upper-layer informationabout a service link, and implementing establishment of an NFV networkservice link.

Embodiment 4

This embodiment provides a method for service implementation in an NFVsystem. As shown in FIG. 10, the method includes:

1001: An NFVO receives information about a service link template throughwhich a service route passes.

The service link template information is used to indicate acorrespondence between a service link identifier and information about aservice link.

In this embodiment, the NFVO first receives information about a servicelink template through which a service route passes, where the servicelink template information is generated and maintained by an OSS/BSS, andis use to indicate a correspondence between a service link identifierand information about a service link.

In this embodiment, the service link template information may includeinformation such as a service link identifier and a sequence of VNFscorresponding to a service link. For a specific example, refer to Table2 in Embodiment 3. Details are not repeated herein.

1002: The NFVO sends a route and resource configuration request message,where the route and resource configuration request message carries theservice link template information, to request to perform, according tothe service link template information, route and resource configurationfor a VNF included in a service link in the service link template.

In this embodiment, after receiving the information about the servicelink template through which the service route passes, the NFVO instructsa second communications unit to perform route and resource configurationfor a VNF included in a service link in the service link template.Therefore, the NFVO needs to send a route and resource configurationrequest message, where the route and resource configuration requestmessage carries the service link template information, to request toperform, according to the service link template information, the routeand resource configuration for the VNF included in the service link inthe service link template.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

Certainly, after receiving the information about the service linktemplate through which the service route passes, the NFVO may furthersend information indicating that the service link template informationhas been received, which is not limited in this embodiment.

In addition, in this embodiment, after the NFVO sends the route andresource configuration request message, if the route and resourceconfiguration succeeds, the NFVO may further receive informationindicating that the route and resource configuration succeeds, which isnot limited in this embodiment.

Based on the method for service implementation in an NFV system providedin this embodiment, an NFVO can receive information about a service linktemplate through which a service route passes, where the service linktemplate information is used to indicate a correspondence between aservice link identifier and information about a service link; and thensend a route and resource configuration request message, where the routeand resource configuration request message carries the service linktemplate information, to request to perform, according to the servicelink template information, route and resource configuration for a VNFincluded in a service link in the service link template, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of an NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 5

This embodiment provides a method for service implementation in an NFVsystem. As shown in FIG. 11, the method includes.

1101: A second communications unit receives a route and resourceconfiguration request message, where the route and resourceconfiguration request message carries information about a service linktemplate through which a service route passes, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate.

The service link template information is used to indicate acorrespondence between a service link identifier and information about aservice link.

The second communications unit that executes this embodiment may be aVIM, or may be an NFVI controller, which is not limited in thisembodiment.

For a related description of the NFVI controller, refer to a relateddescription of step 501 in Embodiment 2. Details are not repeatedherein.

In this embodiment, the service link template information may includeinformation such as a service link identifier and a sequence of VNFscorresponding to a service link. For a specific example, refer to Table2 in Embodiment 3. Details are not repeated herein.

In this embodiment, the route and resource configuration request messagereceived by the second communications unit may be sent by a VNFM, or maybe sent by an OSS/BSS, which is not limited in this embodiment.

1102: The second communications unit performs, according to the servicelink template information and information about a physical resource ofan NFVI, the route and resource configuration for the VNF included inthe service link in the service link template.

In this embodiment, after receiving the route and resource configurationrequest message, the second communications unit performs, according tothe service link template information and the information about thephysical resource of the NFVI, the route and resource configuration forthe VNF included in the service link in the service link template.

For a specific manner for the second communications unit to perform theroute and resource configuration for the VNF included in the servicelink in the service link template, refer to a related description ofstep 502 in Embodiment 2. Details are not repeated herein in thisembodiment.

Certainly, after receiving the route and resource configuration requestmessage, if the route and resource configuration succeeds, the secondcommunications unit may further send information indicating that theroute and resource configuration succeeds, which is not limited in thisembodiment.

Based on the method for service implementation in an NFV system providedin this embodiment, a second communications unit receives a route andresource configuration request message, where the route and resourceconfiguration request message carries information about a service linktemplate through which a service route passes, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in the service link in the service linktemplate; and then performs, according to the service link templateinformation and information about a physical resource of an NFVI, theroute and resource configuration for the VNF included in the servicelink in the service link template, implementing a function of obtainingupper-layer information about a service link and guiding route andresource configuration of the NFVI by using the upper-layer informationabout a service link, and implementing establishment of an NFV networkservice link.

Embodiment 6

This embodiment provides a method for service implementation in an NFVsystem. The method is described by using interaction between an OSS/BSS,an NFVO, a VNFM, and a second communications unit as an example. Asshown in FIG. 12, the method includes:

1201: An OSS/BSS obtains information about a service link templatethrough which a service route passes.

The service link template information is used to indicate acorrespondence between a service link identifier and information about aservice link.

1202: The OSS/BSS sends the service link template information to anNFVO.

In this embodiment, for related descriptions of steps 1201 and 1202,refer to related descriptions of step 901 and step 902 in Embodiment 3.Details are not repeated herein.

1203: The NFVO receives the service link template information.

1204: The NFVO sends a route and resource configuration request messageto a second communications unit, where the route and resourceconfiguration request message carries the service link templateinformation, to request to perform, according to the service linktemplate information, route and resource configuration for a VNFincluded in a service link in the service link template.

In this embodiment, for related descriptions of step 1203 and step 1204,refer to related descriptions of steps 1001 and 1002 in Embodiment 4.Details are not repeated herein.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

In this embodiment, the NFVO may directly send the route and resourceconfiguration request message to the second communications unit, or mayfirst send the route and resource configuration request message to aVNFM, and then send the route and resource configuration request messageto the second communications unit by using the VNFM, which is notlimited in this embodiment.

1205: The second communications unit receives the route and resourceconfiguration request message.

1206: The second communications unit performs, according to the servicelink template information carried in the route and resourceconfiguration request message and information about a physical resourceof an NFVI, the route and resource configuration for the VNF included inthe service link in the service link template.

In this embodiment, for related descriptions of step 1205 and step 1206,refer to related descriptions of steps 1101 and 1102 in Embodiment 5.Details are not repeated herein.

1207: The second communications unit sends, to the NFVO, informationindicating that the route and resource configuration succeeds.

In this embodiment, the second communications unit may directly send, tothe NFVO, the information indicating that the route and resourceconfiguration succeeds, or may first send, to the VNFM, the informationindicating that the route and resource configuration succeeds, and thensend, to the NFVO by using the VNFM, the information indicating that theroute and resource configuration succeeds, which is not limited in thisembodiment.

1208: The NFVO receives the information indicating that the route andresource configuration succeeds.

It should be noted that, after step 1203, the NFVO may further send, tothe OSS/BSS, information indicating that the service link templateinformation has been received, which is not limited in this embodiment.

It should be noted that, after step 1208, the NFVO may further send, tothe second communications unit, the information indicating that theroute and resource configuration succeeds, which is not limited in thisembodiment.

It should be noted that, after obtaining the information about theservice link template through which the service route passes, theOSS/BSS interacts with a PCRF to establish a correspondence between aservice link and a user package, so that the PCRF configures useridentification information and a corresponding service link identifier.Exemplarily, a correspondence between a service link identifier and auser package may be shown in Table 3:

TABLE 3 User package Wireless access Service link identifier ApplicationUser level network / Video Gold (G) 3G 1 Facebook Silver (S) 2G 2Browser Bronze (B) 3G 3 . . . . . . . . . . . .

It should be noted that, after successfully performing the route andresource configuration according to the service link templateinformation as instructed by the NFVO, the second communications unitmay forward a service stream. A service stream forwarding process doesnot belong to the protection scope of the embodiments, and therefore isnot described in detail in this embodiment.

Based on the method for service implementation in an NFV system providedin this embodiment, an OSS/BSS obtains information about a service linktemplate through which a service route passes, where the service linktemplate information is used to indicate a correspondence between aservice link identifier and information about a service link; and sendsthe service link template information to an NFVO, so that the NFVOrequests, according to the service link template information, a secondcommunications unit to perform route and resource configuration for aVNF included in a service link in the service link template,implementing a function of obtaining upper-layer information about aservice link and guiding route and resource configuration of an NFVI byusing the upper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 7

This embodiment provides a method for service implementation in an NFVsystem. The method is described by using interaction between a firstcommunications unit, a VNFM, an NFVO, and a second communications unitas an example, where it is assumed that the first communications unit isa VNF. As shown in FIG. 13, the method includes.

1301: A first communications unit obtains a service link rule, where theservice link rule is used to indicate service processing that needs tobe performed.

In this embodiment, the first communications unit is a VNF, and may be aservice link controller, or may be a network node such as a PGW, a PCRF,a TDF, or a traffic classifier, which is not limited in this embodiment.For a related description of the service link controller, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

For a related description of the service link rule, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

1302: The first communications unit determines whether the service linkrule includes information about a service link.

The information about the service link is used to indicate informationabout a VNF through which a service route passes, and the VNF isconfigured for the service processing.

It can be known according to a related description of the service linkrule in step 301 in Embodiment 1 that, the service link rule maydirectly include information about a service link, or may not includeinformation about a service link. Therefore, in this embodiment, afterobtaining the service link rule, the first communications unit firstdetermines whether the service link rule includes the information aboutthe service link. If the service link rule includes the informationabout the service link, step 1303 is performed.

For a related description of the information about the service link,refer to a related description of step 302 in Embodiment 1. Details arenot repeated herein in this embodiment.

1303: If the service link rule includes the information about theservice link, the first communications unit obtains the informationabout the service link included in the service link rule.

1304: The first communications unit sends a route and resourceconfiguration request message to a VNFM, where the route and resourceconfiguration request message carries the information about the servicelink, to request to perform, according to the information about theservice link, route and resource configuration for a VNF included in aservice link.

In this embodiment, after obtaining the information about the servicelink, the first communications unit sends a route and resourceconfiguration request message to a VNFM.

1305: The VNFM receives the route and resource configuration requestmessage.

1306: The VNFM sends the route and resource configuration requestmessage to a second communications unit.

In this embodiment, the VNFM may directly send the route and resourceconfiguration request message to the second communications unit, or mayfirst send the route and resource configuration request message to anNFVO, and the NFVO sends the route and resource configuration requestmessage to the second communications unit, which is not limited in thisembodiment.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

1307: The second communications unit receives the route and resourceconfiguration request message.

1308: The second communications unit performs, according to theinformation about the service link carried in the route and resourceconfiguration request message and information about a physical resourceof an NFVI, service route and resource configuration for the VNFincluded in the service link.

In this embodiment, for a method for the second communications unit toperform, according to the information about the service link carried inthe route and resource configuration request message and the informationabout the physical resource of the NFVI, the service route and resourceconfiguration for the VNF included in the service link, refer to adescription of step 502 in Embodiment 2. Details are not repeatedtherein in this embodiment.

1309: The second communications unit sends, to the VNFM, informationindicating that the route and resource configuration succeeds.

In this embodiment, the second communications unit may directly send, tothe VNFM, the information indicating that the route and resourceconfiguration succeeds, or may first send, to the NFVO, the informationindicating that the route and resource configuration succeeds, and theNFVO sends, to the VNFM, the information indicating that the route andresource configuration succeeds, which is not limited in thisembodiment.

1310: The VNFM receives the information indicating that the route andresource configuration succeeds.

1311: The VNFM sends, to the first communications unit, the informationindicating that the route and resource configuration succeeds.

1312: The first communications unit receives the information indicatingthat the route and resource configuration succeeds.

Optionally, this embodiment provides a method for service implementationin an NFV system. The method is described by using interaction between afirst communications unit, a VNFM, an NFVO, and a second communicationsunit as an example, where it is assumed that the first communicationsunit is a VNF. As shown in FIG. 14A and FIG. 14B, the method includes.

1401: A first communications unit obtains a service link rule, where theservice link rule is used to indicate service processing that needs tobe performed.

In this embodiment, the first communications unit is a VNF, and may be aservice link controller, or may be a network node such as a PGW, a PCRF,a TDF, or a traffic classifier, which is not limited in this embodiment.For a related description of the service link controller, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

For a related description of the service link rule, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

1402: The first communications unit determines whether the service linkrule includes information about a service link.

The information about the service link is used to indicate informationabout a VNF through which a service route passes, and the VNF isconfigured for the service processing.

It can be known according to a related description of the service linkrule in step 301 in Embodiment 1 that, the service link rule maydirectly include information about a service link, or may not includeinformation about a service link. Therefore, in this embodiment, afterobtaining the service link rule, the first communications unit firstdetermines whether the service link rule includes the information aboutthe service link. If the service link rule does not include theinformation about the service link, step 1403 is performed.

For a related description of the information about the service link,refer to a related description of step 302 in Embodiment 1. Details arenot repeated herein in this embodiment.

1403: If the service link rule does not include the information aboutthe service link, the first communications unit determines, according tothe service link rule, a type of a VNF through which a service routepasses and identification information of a VNF included in each VNF typein the type of the VNF.

Exemplarily, assuming that the service link rule includes a serviceroute policy, for example, video optimization, the first communicationsunit needs to determine, according to an instruction of the serviceroute policy, types of VNFs through which the video optimization needsto pass: TCP proxy->Video Cache->NAT and identification information of aVNF included in each VNF type. For example, a VNF for implementing a TCPproxy function includes VNF1 and VNF7; a VNF for implementing a VideoCache function includes VNF2 and VNF8; and a VNF for implementing an NATfunction includes VNF3.

Certainly, the service link rule may directly include the type of theVNF through which the service route passes, which is not limited in thisembodiment.

1404: The first communications unit sends a query request message to aVNFM, where the query request message carries the identificationinformation of the VNF included in each VNF type, to request to query,according to the identification information of the VNF, firstinformation of the VNF included in each VNF type, where the firstinformation is used to indicate a network topology, a node capability,and a status of the NFVI.

In this embodiment, after determining the type of the VNF through whichservice route passes and the identification information of the VNFincluded in each VNF type in the type of the VNF, the firstcommunications unit sends a query request message to a VNFM, to queryfirst information of the VNF included in each VNF type.

Exemplarily, based on the example in step 1403, the first communicationsunit sends a query request message, to query first information of VNF1,VNF7, VNF2, VNF8, and VNF3, where the first information is used toindicate the network topology, a node capability, and a status of theNFVI.

1405: The VNFM receives the query request message.

1406: The VNFM sends the query request message to a secondcommunications unit.

In this embodiment, the VNFM may directly send the query request messageto the second communications unit, or may first send the query requestmessage to an NFVO, and the NFVO sends the query request message to thesecond communications unit, which is not limited in this embodiment.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

1407: The second communications unit receives the query request message.

1408: The second communications unit queries the physical resource ofthe NFVI according to the query request message, and obtains the firstinformation.

Exemplarily, based on the example in step 1403, the secondcommunications unit may separately query the first information of VNF1,VNF7, VNF2, VNF8, and VNF3 and then obtain the first information, forexample, the first information maybe: resource load of VNF1 exceeds apreset threshold, resource load of VNF7, VNF2, and VNF3 is relativelysmall, and resource load of VNF8 is relatively large.

1409: The second communications unit sends the first information to theVNFM.

In this embodiment, the second communications unit may directly send thefirst information to the VNFM, or may first send the first informationto the NFVO, and the NFVO sends the first information to the VNFM, whichis not limited in this embodiment.

1410: The VNFM receives the first information.

1411: The VNFM sends the first information to the first communicationsunit.

1412: The first communications unit receives the first information.

1413: The first communications unit generates the information about theservice link according to the first information.

After receiving the first information, the first communications unitgenerates the information about the service link according to the firstinformation.

Exemplarily, based on the example in step 1408, if the first informationis: resource load of VNF1 exceeds a preset threshold, resource load ofVNF7, VNF2, and VNF3 is relatively small, and resource load of VNF8 isrelatively large, a service link may be generated as follows accordingto the first information:

VNF7->VNF2->VNF3.

It should be noted that, the foregoing example merely exemplarilyprovides a method of obtaining information about a service linkaccording to a service link rule, and certainly, according to differentservice link rules, information about a service link obtained afterquery of the second communications unit may be different, which is notlimited in this embodiment.

1414: The first communications unit sends a route and resourceconfiguration request message to the VNFM, where the route and resourceconfiguration request message carries the information about the servicelink, to request to perform, according to the information about theservice link, route and resource configuration for the VNF included in aservice link.

1415: The VNFM receives the route and resource configuration requestmessage.

1416: The VNFM sends the route and resource configuration requestmessage to the second communications unit.

1417: The second communications unit receives the route and resourceconfiguration request message.

1418: The second communications unit performs service route and resourceconfiguration according to the information about the service linkcarried in the route and resource configuration request message andinformation about the physical resource of the NFVI.

1419: The second communications unit sends, to the VNFM, informationindicating that the route and resource configuration succeeds.

1420: The VNFM receives the information indicating that the route andresource configuration succeeds.

1421: The VNFM sends, to the first communications unit, the informationindicating that the route and resource configuration succeeds.

1422: The first communications unit receives the information indicatingthat the route and resource configuration succeeds.

In this embodiment, for related descriptions of steps 1414 to 1422,refer to descriptions of steps 1304 to 1312 in the embodiment shown inFIG. 13. Details are not repeated herein in this embodiment.

This embodiment further provides a method for service implementation inan NFV system. The method is described by using interaction between afirst communications unit, an OSS/BSS, a VNFM, an NFVO, and a secondcommunications unit as an example, where the first communications unitmay be a VNF, or may be a PNF, which is not limited in this embodiment.As shown in FIG. 15, the method includes:

1501: A first communications unit obtains a service link rule, where theservice link rule is used to indicate service processing that needs tobe performed.

In this embodiment, the first communications unit may be a service linkcontroller, or may be a network node such as a PGW, a PCRF, a TDF, or atraffic classifier, which is not limited in this embodiment. For arelated description of the service link controller, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

It should be noted that, in this embodiment, the network node such asthe PGW, the PCRF, the TDF, or the traffic classifier may be a VNF unit,or may be a PNF unit, which is not limited in this embodiment.

For a related description of the service link rule, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

1502: The first communications unit determines whether the service linkrule includes information about a service link.

The information about the service link is used to indicate informationabout a VNF through which a service route passes, and the VNF isconfigured for the service processing.

It can be known according to a related description of the service linkrule in step 301 in Embodiment 1 that, the service link rule maydirectly include information about a service link, or may not includeinformation about a service link. Therefore, in this embodiment, afterobtaining the service link rule, the first communications unit firstdetermines whether the service link rule includes the information aboutthe service link. If the service link rule includes the informationabout the service link, step 1503 is performed.

For a related description of the information about the service link,refer to a related description of step 302 in Embodiment 1. Details arenot repeated herein in this embodiment.

1503: If the service link rule includes the information about theservice link, the first communications unit obtains the informationabout the service link included in the service link rule.

1504: The first communications unit sends a route and resourceconfiguration request message to an OSS/BSS, where the route andresource configuration request message carries the information about theservice link, to request to perform, according to the information aboutthe service link, route and resource configuration for a VNF included ina service link.

In this embodiment, after obtaining the information about the servicelink, the first communications unit sends a route and resourceconfiguration request message to an OSS/BSS.

1505: The OSS/BSS receives the route and resource configuration requestmessage.

1506: The OSS/BSS sends the route and resource configuration requestmessage to an NFVO.

1507: The NFVO receives the route and resource configuration requestmessage.

1508: The NFVO sends the route and resource configuration requestmessage to a second communications unit.

In this embodiment, the NFVO may directly send the route and resourceconfiguration request message to the second communications unit, or mayfirst send the route and resource configuration request message to aVNFM, and the VNFM sends the route and resource configuration requestmessage to the second communications unit, which is not limited in thisembodiment.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

1509: The second communications unit receives the route and resourceconfiguration request message.

1510: The second communications unit performs, according to theinformation about the service link carried in the route and resourceconfiguration request message and information about a physical resourceof an NFVI, service route and resource configuration for the VNFincluded in the service link.

In this embodiment, for a method for the second communications unit toperform, according to the information about the service link carried inthe route and resource configuration request message and the informationabout the physical resource of the NFVI, the service route and resourceconfiguration for the VNF included in the service link, refer to adescription of step 502 in Embodiment 2. Details are not repeatedtherein in this embodiment.

1511: The second communications unit sends, to the NFVO, informationindicating that the route and resource configuration succeeds.

In this embodiment, the second communications unit may directly send, tothe NFVO, the information indicating that the route and resourceconfiguration succeeds, or may first send, to the VNFM, the informationindicating that the route and resource configuration succeeds, and theVNFM sends, to the NFVO, the information indicating that the route andresource configuration succeeds, which is not limited in thisembodiment.

1512: The NFVO receives the information indicating that the route andresource configuration succeeds.

1513: The NFVO sends, to the OSS/BSS, the information indicating thatthe route and resource configuration succeeds.

1514: The OSS/BSS receives the information indicating that the route andresource configuration succeeds.

1515: The OSS/BSS sends, to the first communications unit, theinformation indicating that the route and resource configurationsucceeds.

1516: The first communications unit receives the information indicatingthat the route and resource configuration succeeds.

Optionally, this embodiment further provides a method for serviceimplementation in an NFV system. The method is described by usinginteraction between a first communications unit, an OSS/BSS, a VNFM, anNFVO, and a second communications unit as an example, where the firstcommunications unit may be a VNF, or may be a PNF, which is not limitedin this embodiment. As shown in FIG. 16A and FIG. 16B, the methodincludes.

1601: A first communications unit obtains a service link rule, where theservice link rule is used to indicate service processing that needs tobe performed.

In this embodiment, the first communications unit may be a service linkcontroller, or may be a network node such as a PGW, a PCRF, a TDF, or atraffic classifier, which is not limited in this embodiment. For arelated description of the service link controller, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

It should be noted that, in this embodiment, the network node such asthe PGW, the PCRF, the TDF, or the traffic classifier may be a VNF unit,or may be a PNF unit, which is not limited in this embodiment.

For a related description of the service link rule, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

1602: The first communications unit determines whether the service linkrule includes information about a service link.

The information about the service link is used to indicate informationabout a VNF through which a service route passes, and the VNF isconfigured for the service processing.

It can be known according to a related description of the service linkrule in step 301 in Embodiment 1 that, the service link rule maydirectly include information about a service link, or may not includeinformation about a service link. Therefore, in this, after obtainingthe service link rule, the first communications unit first determineswhether the service link rule includes the information about the servicelink. If the service link rule does not include the information aboutthe service link, step 1603 is performed.

For a related description of the information about the service link,refer to a related description of step 302 in Embodiment 1. Details arenot repeated herein in this embodiment.

1603: If the service link rule does not include the information aboutthe service link, the first communications unit determines, according tothe service link rule, a type of a VNF through which a service routepasses and identification information of a VNF included in each VNF typein the type of the VNF.

1604: The first communications unit sends a query request message to anOSS/BSS, where the query request message carries the identificationinformation of the VNF included in each VNF type, to request to query,according to the identification information of the VNF, firstinformation of the VNF included in each VNF type, where the firstinformation is used to indicate a network topology, a node capability,and a status of an NFVI.

1605: The OSS/BSS receives the query request message.

1606: The OSS/BSS sends the query request message to an NFVO.

1607: The NFVO receives the query request message.

1608: The NFVO sends the query request message to a secondcommunications unit.

In this embodiment, the NFVO may directly send the query request messageto the second communications unit, or may first send the query requestmessage to a VNFM, and the VNFM sends the query request message to thesecond communications unit, which is not limited in this embodiment.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

1609: The second communications unit receives the query request message.

1610: The second communications unit queries the physical resource ofthe NFVI according to the query request message, and obtains the firstinformation.

1611: The second communications unit sends the first information to theNFVO.

In this embodiment, the second communications unit may directly send thefirst information to the NFVO, or may first send the first informationto the VNFM, and the VNFM sends the first information to the NFVO, whichis not limited in this embodiment.

1612: The NFVO receives the first information.

1613: The NFVO sends the first information to the OSS/BSS.

1614: The OSS/BSS receives the first information.

1615: The OSS/BSS sends the first information to the firstcommunications unit.

1616: The first communications unit receives the first information.

1617: The first communications unit generates the information about theservice link according to the first information.

In this embodiment, for an example in which the first communicationsunit obtains the information about the service link after querying thesecond communications unit according to the service link rule, refer tothe example in the embodiment shown in FIG. 14A and FIG. 14B in whichthe first communications unit obtains the information about the servicelink after querying the second communications unit according to theservice link rule. Details are not repeated herein in this embodiment.

1618: The first communications unit sends a route and resourceconfiguration request message to the OSS/BSS, where the route andresource configuration request message carries the information about theservice link, to request to perform, according to the information aboutthe service link, route and resource configuration for the VNF includedin a service link.

1619: The OSS/BSS receives the route and resource configuration requestmessage.

1620: The OSS/BSS sends the route and resource configuration requestmessage to the NFVO.

1621: The NFVO receives the route and resource configuration requestmessage.

1622: The NFVO sends the route and resource configuration requestmessage to the second communications unit.

1623: The second communications unit receives the route and resourceconfiguration request message.

1624: The second communications unit performs service route and resourceconfiguration according to the information about the service linkcarried in the route and resource configuration request message andinformation about the physical resource of the NFVI.

1625: The second communications unit sends, to the NFVO, informationindicating that the route and resource configuration succeeds.

1626: The NFVO receives the information indicating that the route andresource configuration succeeds.

1627: The NFVO sends, to the OSS/BSS, the information indicating thatthe route and resource configuration succeeds.

1628: The OSS/BSS receives the information indicating that the route andresource configuration succeeds.

1629: The OSS/BSS sends, to the first communications unit, theinformation indicating that the route and resource configurationsucceeds.

1630: The first communications unit receives the information indicatingthat the route and resource configuration succeeds.

In this embodiment, for related descriptions of steps 1418 to 1430,refer to descriptions of steps 1304 to 1316 in the embodiment shown inFIG. 15. Details are not repeated herein in this embodiment.

It should be noted that, in the embodiment shown in FIG. 13 or FIG. 15,when the service link rule includes the information about the servicelink, the first communications unit may also query, by using the secondcommunications unit, the first information of the VNF included in theservice link, to determine whether a state of the VNF included in theservice link is abnormal. When the second communications unit obtainsthrough query that a state of a VNF included in the service link isabnormal (for example, resource load exceeds a preset threshold), thesecond communications unit feeds back abnormality information to thefirst communications unit in time, so that the first communications unitfeeds back the abnormality information to an entity that sends theservice link rule, and the entity that sends the service link rule thenperforms corresponding processing according to a corresponding policy,for example, re-sends information about a service link. Whether thefirst information of the VNF included in the service link needs to bequeried by using the second communications unit when the service linkrule includes the information about the service link is not limited inthis embodiment n.

It should be noted that, as described above, in the embodiments shown inFIG. 13 to FIG. 16A and FIG. 16B, the second communications unit may bea VIM, or may be an NFVI controller. If the second communications unitis an NFVI controller, a unit that directly communicates with the NFVIcontroller is generally a VIM, that is, a previous-hop communicationsunit of the NFVI controller is generally a VIM. Exemplarily, forexample, in step 1306 in the embodiment shown in FIG. 13, when the VNFMsends the route and resource configuration request message to the secondcommunications unit, a specific implementation path may be: sending, bythe VNFM, the route and resource configuration request message to a VIM,and sending, by the VIM, the route and resource configuration requestmessage to the NFVI controller, which is not limited in this embodiment.

Based on the method for service implementation in an NFV system providedin this embodiment, after obtaining a service link rule, a firstcommunications unit can obtain, according to the service link rule,information about a service link through which a service route passes,and then send a route and configuration request message that carries theinformation about the service link, to request to perform, according tothe information about the service link, route and resource configurationfor a VNF included in the service link, implementing a function ofobtaining upper-layer information about a service link and guiding routeand resource configuration of an NFVI by using the upper-layerinformation about a service link, and implementing establishment of anNFV network service link.

Embodiment 8

This embodiment provides a first communications unit 1700. As shown inFIG. 17, the first communications unit 1700 includes: a service linkrule obtaining unit 1701, a service link information obtaining unit1702, and a message sending unit 1703, where the service link ruleobtaining unit 1701 is configured to obtain a service link rule, wherethe service link rule is used to indicate service processing that needsto be performed; the service link information obtaining unit 1702 isconfigured to obtain, according to the service link rule obtained by theservice link rule obtaining unit 1701, information about a service linkthrough which a service route passes, where the information about theservice link is used to indicate information about a VNF through whichthe service route passes, and the VNF is configured for the serviceprocessing; and the message sending unit 1703 is configured to send aroute and resource configuration request message, where the route andresource configuration request message carries the information about theservice link obtained by the service link information obtaining unit1702, to request to perform, according to the information about theservice link, route and resource configuration for the VNF included inthe service link.

Further, as shown in FIG. 18, the first communications unit 1700 furtherincludes an information determining unit 1704, where the informationdetermining unit 1704 is configured to: before the service linkinformation obtaining unit 1702 obtains, according to the service linkrule obtained by the service link rule obtaining unit 1701, theinformation about the service link through which the service routepasses, determine whether the service link rule includes the informationabout the service link; and the service link information obtaining unit1702 includes: an information determining module 17021, a messagesending module 17022, a receiving module 17023, and a generation module17024, where the information determining module 17021 is configured to:if the information determining unit 1704 determines that the servicelink rule does not include the information about the service link,determine, according to the service link rule, a type of the VNF throughwhich the service route passes and identification information of a VNFincluded in each VNF type in the type of the VNF; the message sendingmodule 17022 is configured to send a query request message, where thequery request message carries the identification information, determinedby the information determining module 17021, of the VNF included in eachVNF type, to request to query, according to the identificationinformation of the VNF, first information of the VNF included in eachVNF type, where the first information is used to indicate a networktopology, a node capability, and a status of a network functionvirtualization infrastructure (NFVI); the receiving module 17023 isconfigured to receive the first information of the VNF included in eachVNF type; and the generation module 17024 is configured to generate theinformation about the service link according to the first information,received by the receiving module 17023, of the VNF included in each VNFtype.

Further, as shown in FIG. 19, the service link information obtainingunit 1702 further includes an obtaining module 17025, where theobtaining module 17025 is configured to: if the service link ruleincludes the information about the service link, obtain the informationabout the service link included in the service link rule.

Further, the message sending module 17022 is configured to: send thequery request message to a second communications unit, to request thesecond communications unit to query, according to the identificationinformation of the VNF, the first information of the VNF included ineach VNF type.

In a possible implementation manner, the message sending module 17022 isconfigured to: send the query request message to a VNF manager (VNFM),to send the query request message to the second communications unit byusing the VNFM.

Preferably, the message sending module 17022 is configured to: send thequery request message to the VNFM, to send the query request message toa NFV orchestrator (NFVO) by using the VNFM and to send the queryrequest message to the second communications unit by using the NFVO.

In another possible implementation manner, the message sending module17022 is configured to: send the query request message to an operationssupport system/business support system (OSS/BSS), to send the queryrequest message to an NFVO by using the OSS/BSS and to send the queryrequest message to the second communications unit by using the NFVO.

Preferably, the message sending module 17022 is configured to: send thequery request message to the OSS/BSS, to send the query request messageto the NFVO by using the OSS/BSS, to send the query request message to aVNFM by using the NFVO, and to send the query request message to thesecond communications unit by using the VNFM.

Further, the message sending unit 1703 is configured to: send the routeand resource configuration request message to the second communicationsunit, to request the second communications unit to perform the route andresource configuration.

In a possible implementation manner, the message sending unit 1703 isconfigured to: send the route and resource configuration request messageto the VNFM, to send the route and resource configuration requestmessage to the second communications unit by using the VNFM.

Preferably, the message sending unit 1703 is configured to: send theroute and resource configuration request message to the VNFM, to sendthe route and resource configuration request message to the NFVO byusing the VNFM and to send the route and resource configuration requestmessage to the second communications unit by using the NFVO.

In another possible implementation manner, the message sending unit 1703is configured to: send the route and resource configuration requestmessage to the OSS/BSS, to send the route and resource configurationrequest message to the NFVO by using the OSS/BSS and to send the routeand resource configuration request message to the second communicationsunit by using the NFVO.

Preferably, the message sending unit 1703 is configured to: send theroute and resource configuration request message to the OSS/BSS, to sendthe route and resource configuration request message to the NFVO byusing the OSS/BSS, to send the route and resource configuration requestmessage to the VNFM by using the NFVO, and to send the route andresource configuration request message to the second communications unitby using the VNFM.

Further, as shown in FIG. 20, the first communications unit 1700 furtherincludes a receiving unit 1705, where the receiving unit 1705 isconfigured to: if the route and resource configuration succeeds, receiveinformation indicating that the route and resource configurationsucceeds.

In this embodiment, the first communications unit may be a service linkcontroller, or may be a network node such as a PGW, a PCRF, a TDF, or atraffic classifier, which is not limited in this embodiment. For arelated description of the service link controller, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

It should be noted that, in this embodiment, the network node such asthe PGW, the PCRF, the TDF, or the traffic classifier may be a VNF unit,or may be a PNF unit, which is not limited in this embodiment.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the first communications unit, refer to a description ofEmbodiment 1 or Embodiment 7. Details are not repeated herein in thisembodiment.

Based on the first communications unit provided in this embodiment,after obtaining a service link rule, the first communications unit canobtain, according to the service link rule, information about a servicelink through which a service route passes, and then send a route andconfiguration request message that carries the information about theservice link, to request to perform, according to the information aboutthe service link, route and resource configuration for a VNF included inthe service link, implementing a function of obtaining upper-layerinformation about a service link and guiding route and resourceconfiguration of an NFVI by using the upper-layer information about aservice link, and implementing establishment of an NFV network servicelink.

Embodiment 9

This embodiment provides a second communications unit 2100. As shown inFIG. 21, the second communications unit 2100 includes: a receiving unit2101 and a configuration unit 2102, where the receiving unit 2101 isconfigured to receive a route and resource configuration requestmessage, where the route and resource configuration request messagecarries information about a service link through which a service routepasses, to request to perform, according to the information about theservice link, route and resource configuration for a VNF included in theservice link, where the information about the service link is obtainedaccording to a service link rule, the service link rule is used toindicate service processing that needs to be performed, the informationabout the service link is used to indicate information about the VNFthrough which the service route passes, and the VNF is configured forthe service processing; and the configuration unit 2102 is configured toperform, according to the information about the service link received bythe receiving unit 2101 and information about a physical resource of aNFVI, service route and resource configuration for the VNF included inthe service link.

Further, as shown in FIG. 22, the second communications unit 2100further includes: a query unit 2103 and a sending unit 2104, where thereceiving unit 2101 is further configured to: before receiving the routeand resource configuration request message, receive a query requestmessage, where the query request message carries identificationinformation of a VNF included in each VNF type in a type of the VNFthrough which the service route passes, to request to query, accordingto the identification information of the VNF, first information of theVNF included in each VNF type, where the first information is used toindicate a network topology, a node capability, and a status of theNFVI; the query unit 2103 is configured to: according to the queryrequest message received by the receiving unit 2101, query the physicalresource of the NFVI, and obtain the first information of the VNFincluded in each VNF type; and the sending unit 2104 is configured tosend the first information, obtained by the query unit 2103 throughquery, of the VNF included in each VNF type, to generate the informationabout the service link according to the first information of the VNFincluded in each VNF type.

In a possible implementation manner, the receiving unit 2101 isconfigured to: receive the route and resource configuration requestmessage sent by a VNFM.

In another possible implementation manner, the receiving unit 2101 isconfigured to: receive the route and resource configuration requestmessage sent by a VNF OSS/BSS.

Further, the sending unit 2104 is further configured to: if the routeand resource configuration succeeds, send information indicating thatthe route and resource configuration succeeds.

In this embodiment, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment. For arelated description of the NFVI controller, refer to the part of step501 in Embodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the second communications unit, refer to a description ofEmbodiment 2 or Embodiment 7. Details are not repeated herein in thisembodiment.

Based on the second communications unit provided in this embodiment, thesecond communications unit can receive a route and resourceconfiguration request message, where the route and resourceconfiguration request message carries information about a service linkthrough which a service route passes, to request to perform, accordingto the information about the service link, route and resourceconfiguration for a VNF included in the service link; and then perform,according to the information about the service link and informationabout a physical resource of an NFVI, service route and resourceconfiguration for the VNF included in the service link, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of the NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 10

This embodiment provides an OSS/BSS 2300. As shown in FIG. 23, theOSS/BSS 2300 includes: an obtaining unit 2301 and a sending unit 2302,where the obtaining unit 2301 is configured to obtain information abouta service link template through which a service route passes, where theservice link template information is used to indicate a correspondencebetween a service link identifier and information about a service link;and the sending unit 2302 is configured to send the service linktemplate information obtained by the obtaining unit 2301 to an NFVorchestrator NFVO, so that the NFVO requests, according to the servicelink template information, to perform route and resource configurationfor a VNF included in a service link in the service link template.

Further, as shown in FIG. 24, the OSS/BSS 2300 further includes areceiving unit 2303, where the receiving unit 2303 is configured toreceive information indicating that the service link templateinformation has been received.

Further, the receiving unit 2303 is further configured to: if the routeand resource configuration succeeds, receive information indicating thatthe route and resource configuration succeeds.

For the method for service implementation in an NFV system that isperformed by the OSS/BSS, refer to a description of Embodiment 3 orEmbodiment 6. Details are not repeated herein in this embodiment.

Based on the OSS/BSS provided in this embodiment, the OSS/BSS obtainsinformation about a service link template through which a service routepasses, where the service link template information is used to indicatea correspondence between a service link identifier and information abouta service link; and sends the service link template information to anNFVO, so that the NFVO requests, according to the service link templateinformation, to perform route and resource configuration for a VNFincluded in a service link in the service link template, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of an NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 11

This embodiment provides a NFVO 2500. As shown in FIG. 25, the NFVO 2500includes: a receiving unit 2501 and a sending unit 2502, where thereceiving unit 2501 is configured to receive information about a servicelink template through which a service route passes, where the servicelink template information is used to indicate a correspondence between aservice link identifier and information about a service link; and thesending unit 2502 is configured to send a route and resourceconfiguration request message, where the route and resourceconfiguration request message carries the service link templateinformation received by the receiving unit 2501, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate.

The sending unit 2502 may be configured to: send the route and resourceconfiguration request message to a second communications unit, torequest the second communications unit to perform, according to theservice link template information, the route and resource configurationfor the VNF included in the service link in the service link template.

Further, the sending unit 2502 is further configured to: after thereceiving unit 2501 receives the information about the service linktemplate through which the service route passes, send informationindicating that the service link template information has been received.

Further, the receiving unit 2501 is further configured to: if the routeand resource configuration succeeds, receive information indicating thatthe route and resource configuration succeeds.

In this embodiment, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment. For arelated description of the NFVI controller, refer to the part of step501 in Embodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the NFVO, refer to a description of Embodiment 4 orEmbodiment 6. Details are not repeated herein in this embodiment.

Based on the NFVO provided in this embodiment, the NFVO can receiveinformation about a service link template through which a service routepasses, where the service link template information is used to indicatea correspondence between a service link identifier and information abouta service link; and then send a route and resource configuration requestmessage, where the route and resource configuration request messagecarries the service link template information, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate, implementing a function of obtaining upper-layer informationabout a service link and guiding route and resource configuration of anNFVI by using the upper-layer information about a service link, andimplementing establishment of an NFV network service link.

Embodiment 12

This embodiment provides a second communications unit 2600. As shown inFIG. 26, the second communications unit 2600 includes: a receiving unit2601 and a configuration unit 2602, where the receiving unit 2601 isconfigured to receive a route and resource configuration requestmessage, where the route and resource configuration request messagecarries information about a service link template through which aservice route passes, to request to perform, according to the servicelink template information, route and resource configuration for a VNFincluded in a service link in the service link template, where theservice link template information is used to indicate a correspondencebetween a service link identifier and information about a service link;and the configuration unit 2602 is configured to perform, according tothe service link template information received by the receiving unit2601 and information about a physical resource of a NFVI, the route andresource configuration for the VNF included in the service link in theservice link template.

The receiving unit 2601 may be configured to: receive the route andresource configuration request message sent by an NFV orchestrator NFVO.

Further, as shown in FIG. 27, the second communications unit 2600further includes a sending unit 2603, where the sending unit 2603 isconfigured to: if the route and resource configuration succeeds, sendinformation indicating that the route and resource configurationsucceeds.

In this embodiment, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment. For arelated description of the NFVI controller, refer to the part of step501 in Embodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the second communications unit, refer to a description ofEmbodiment 5 or Embodiment 6. Details are not repeated herein in thisembodiment.

Based on the second communications unit provided in this embodiment, thesecond communications unit receives a route and resource configurationrequest message, where the route and resource configuration requestmessage carries information about a service link template through whicha service route passes, to request to perform, according to the servicelink template information, route and resource configuration for a VNFincluded in the service link in the service link template; and thenperforms, according to the service link template information andinformation about a physical resource of an NFVI, the route and resourceconfiguration for the VNF included in the service link in the servicelink template, implementing a function of obtaining upper-layerinformation about a service link and guiding route and resourceconfiguration of the NFVI by using the upper-layer information about aservice link, and implementing establishment of an NFV network servicelink.

Embodiment 13

This embodiment provides a first communications unit 2800. As shown inFIG. 28, the first communications unit 2800 includes: a processor 2802and a transmitter 2803, where the processor 2802 is configured to obtaina service link rule, where the service link rule is used to indicateservice processing that needs to be performed; the processor 2802 isfurther configured to obtain, according to the service link rule,information about a service link through which a service route passes,where the information about the service link is used to indicateinformation about a VNF through which the service route passes, and theVNF is configured for the service processing; and the transmitter 2803is configured to send a route and resource configuration requestmessage, where the route and resource configuration request messagecarries the information about the service link obtained by the processor2802, to request to perform, according to the information about theservice link, route and resource configuration for the VNF included inthe service link.

Further, the processor 2802 is further configured to: before obtaining,according to the service link rule, the information about the servicelink through which the service route passes, determine whether theservice link rule includes the information about the service link; andthe processor 2802 being further configured to obtain, according to theservice link rule, information about a service link through which aservice route passes includes: if the service link rule does not includethe information about the service link, determining, according to theservice link rule, a type of the VNF through which the service routepasses and identification information of a VNF included in each VNF typein the type of the VNF; sending a query request message, where the queryrequest message carries the identification information of the VNFincluded in each VNF type, to request to query, according to theidentification information of the VNF, first information of the VNFincluded in each VNF type, where the first information is used toindicate a network topology, a node capability, and a status of a NFVI;receiving the first information of the VNF included in each VNF type;and generating the information about the service link according to thefirst information of the VNF included in each VNF type.

Further, the processor 2802 being configured to obtain, according to theservice link rule, information about a service link through which aservice route passes further includes:

if the service link rule includes the information about the servicelink, obtaining the information about the service link included in theservice link rule.

The sending, by the processor 2802, a query request message may include:sending the query request message to a second communications unit, torequest the second communications unit to query, according to theidentification information of the VNF, the first information of the VNFincluded in each VNF type.

In a possible implementation manner, the sending, by the processor 2802,a query request message includes: sending the query request message to aVNFM, to send the query request message to the second communicationsunit by using the VNFM.

Preferably, the sending, by the processor 2802, a query request messageincludes: sending the query request message to the VNFM, to send thequery request message to a NFVO by using the VNFM and to send the queryrequest message to the second communications unit by using the NFVO.

In a possible implementation manner, the sending, by the processor 2802,a query request message includes: sending the query request message toan OSS/BSS, to send the query request message to an NFVO by using theOSS/BSS and to send the query request message to the secondcommunications unit by using the NFVO.

Preferably, the sending, by the processor 2802, a query request messageincludes: sending the query request message to the OSS/BSS, to send thequery request message to the NFVO by using the OSS/BSS, to send thequery request message to a VNFM by using the NFVO, and to send the queryrequest message to the second communications unit by using the VNFM.

Further, the transmitter 2803 is configured to: send the route andresource configuration request message to the second communicationsunit, to request the second communications unit to perform the route andresource configuration.

In a possible implementation manner, the transmitter 2803 is configuredto: send the route and resource configuration request message to theVNFM, to send the route and resource configuration request message tothe second communications unit by using the VNFM.

Preferably, the transmitter 2803 is configured to: send the route andresource configuration request message to the VNFM, to send the routeand resource configuration request message to the NFVO by using the VNFMand to send the route and resource configuration request message to thesecond communications unit by using the NFVO.

In another possible implementation manner, the transmitter 2803 isconfigured to:

send the route and resource configuration request message to theOSS/BSS, to send the route and resource configuration request message tothe NFVO by using the OSS/BSS and to send the route and resourceconfiguration request message to the second communications unit by usingthe NFVO.

Preferably, the transmitter 2803 is configured to: send the route andresource configuration request message to the OSS/BSS, to send the routeand resource configuration request message to the NFVO by using theOSS/BSS, to send the route and resource configuration request message tothe VNFM by using the NFVO, and to send the route and resourceconfiguration request message to the second communications unit by usingthe VNFM.

Further, as shown in FIG. 29, the first communications unit 2800 furtherincludes a receiver 2804, where the receiver 2804 is configured to: ifthe route and resource configuration succeeds, receive informationindicating that the route and resource configuration succeeds.

In this embodiment, the first communications unit may be a service linkcontroller, or may be a network node such as a PGW, a PCRF, a TDF, or atraffic classifier, which is not limited in this embodiment. For arelated description of the service link controller, refer to adescription of step 301 in Embodiment 1. Details are not repeated hereinin this embodiment.

It should be noted that, in this embodiment, the network node such asthe PGW, the PCRF, the TDF, or the traffic classifier may be a VNF unit,or may be a PNF unit, which is not limited in this embodiment.

The second communications unit may be a VIM, or may be an NFVIcontroller, which is not limited in this embodiment. For a relateddescription of the NFVI controller, refer to the part of step 501 inEmbodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the first communications unit, refer to a description ofEmbodiment 1 or Embodiment 7. Details are not repeated herein in thisembodiment.

Based on the first communications unit provided in this embodiment,after obtaining a service link rule, the first communications unit canobtain, according to the service link rule, information about a servicelink through which a service route passes, and then send a route andconfiguration request message that carries the information about theservice link, to request to perform, according to the information aboutthe service link, route and resource configuration for a VNF included inthe service link, implementing a function of obtaining upper-layerinformation about a service link and guiding route and resourceconfiguration of an NFVI by using the upper-layer information about aservice link, and implementing establishment of an NFV network servicelink.

Embodiment 14

This embodiment provides a second communications unit 3000. As shown inFIG. 30, the second communications unit 3000 includes: a receiver 3002and a processor 3003, where the receiver 3002 is configured to receive aroute and resource configuration request message, where the route andresource configuration request message carries information about aservice link through which a service route passes, to request toperform, according to the information about the service link, route andresource configuration for a VNF included in the service link, where theinformation about the service link is obtained according to a servicelink rule, the service link rule is used to indicate service processingthat needs to be performed, the information about the service link isused to indicate information about the VNF through which the serviceroute passes, and the VNF is configured for the service processing; andthe processor 3003 is configured to perform, according to theinformation about the service link received by the receiver 3002 andinformation about a physical resource of a NFVI, service route andresource configuration for the VNF included in the service link.

Further, as shown in FIG. 31, the second communications unit 3000further includes: a transmitter 3004, where the receiver 3002 is furtherconfigured to: before receiving the route and resource configurationrequest message, receive a query request message, where the queryrequest message carries identification information of a VNF included ineach VNF type in a type of the VNF through which the service routepasses, to request to query, according to the identification informationof the VNF, first information of the VNF included in each VNF type,where the first information is used to indicate a network topology, anode capability, and a status of the NFVI; the processor 3003 is furtherconfigured to: according to the query request message received by thereceiver 3002, query the physical resource of the NFVI, and obtain thefirst information of the VNF included in each VNF type; and thetransmitter 3004 is configured to send the first information, obtainedby the processor 3003 through query, of the VNF included in each VNFtype, to generate the information about the service link according tothe first information of the VNF included in each VNF type.

In a possible implementation manner, the receiver 3002 may be configuredto: receive the route and resource configuration request message sent bya VNFM.

In another possible implementation manner, the receiver 3002 isconfigured to: receive the route and resource configuration requestmessage sent by a VNF OSS/BSS.

Further, the transmitter 3004 is further configured to: if the route andresource configuration succeeds, send information indicating that theroute and resource configuration succeeds.

In this embodiment, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment. For arelated description of the NFVI controller, refer to the part of step501 in Embodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the second communications unit, refer to a description ofEmbodiment 2 or Embodiment 7. Details are not repeated herein in thisembodiment.

Based on the second communications unit provided in this embodiment, thesecond communications unit can receive a route and resourceconfiguration request message, where the route and resourceconfiguration request message carries information about a service linkthrough which a service route passes, to request to perform, accordingto the information about the service link, route and resourceconfiguration for a VNF included in the service link; and then perform,according to the information about the service link and informationabout a physical resource of an NFVI, service route and resourceconfiguration for the VNF included in the service link, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of the NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 15

This embodiment provides an 3200. As shown in FIG. 32, the OSS/BSS 3200includes: a processor 3202 and a transmitter 3203, where the processor3202 is configured to obtain information about a service link templatethrough which a service route passes, where the service link templateinformation is used to indicate a correspondence between a service linkidentifier and information about a service link; and the transmitter3203 is configured to send the service link template informationobtained by the processor 3202 to an NFV orchestrator NFVO, so that theNFVO requests, according to the service link template information, toperform route and resource configuration for a VNF included in a servicelink in the service link template.

Further, as shown in FIG. 33, the OSS/BSS 3200 further includes areceiver 3204, where the receiver 3204 is configured to receiveinformation indicating that the service link template information hasbeen received.

Further, the receiver 3204 is further configured to: if the route andresource configuration succeeds, receive information indicating that theroute and resource configuration succeeds.

For the method for service implementation in an NFV system that isperformed by the OSS/BSS, refer to a description of Embodiment 3 orEmbodiment 6. Details are not repeated herein in this embodiment.

Based on the OSS/BSS provided in this embodiment, the OSS/BSS obtainsinformation about a service link template through which a service routepasses, where the service link template information is used to indicatea correspondence between a service link identifier and information abouta service link; and sends the service link template information to anNFVO, so that the NFVO requests, according to the service link templateinformation, to perform route and resource configuration for a VNFincluded in a service link in the service link template, implementing afunction of obtaining upper-layer information about a service link andguiding route and resource configuration of an NFVI by using theupper-layer information about a service link, and implementingestablishment of an NFV network service link.

Embodiment 16

This embodiment provides a NFVO 3400. As shown in FIG. 34, the NFVO 3400includes: a receiver 3402 and a transmitter 3403, where the receiver3402 is configured to receive information about a service link templatethrough which a service route passes, where the service link templateinformation is used to indicate a correspondence between a service linkidentifier and information about a service link; and the transmitter3403 is configured to send a route and resource configuration requestmessage, where the route and resource configuration request messagecarries the service link template information received by the receiver3402, to request to perform, according to the service link templateinformation, route and resource configuration for a VNF included in aservice link in the service link template.

The transmitter 3403 may be configured to: send the route and resourceconfiguration request message to a second communications unit, torequest the second communications unit to perform, according to theservice link template information, the route and resource configurationfor the VNF included in the service link in the service link template.

Further, the transmitter 3403 is further configured to: after thereceiver 3402 receives the information about the service link templatethrough which the service route passes, send information indicating thatthe service link template information has been received.

Further, the receiver 3402 is further configured to: if the route andresource configuration succeeds, receive information indicating that theroute and resource configuration succeeds.

In this embodiment, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment. For arelated description of the NFVI controller, refer to the part of step501 in Embodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the NFVO, refer to a description of Embodiment 4 orEmbodiment 6. Details are not repeated herein in this embodiment.

Based on the NFVO provided in this embodiment, the NFVO can receiveinformation about a service link template through which a service routepasses, where the service link template information is used to indicatea correspondence between a service link identifier and information abouta service link; and then send a route and resource configuration requestmessage, where the route and resource configuration request messagecarries the service link template information, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate, implementing a function of obtaining upper-layer informationabout a service link and guiding route and resource configuration of anNFVI by using the upper-layer information about a service link, andimplementing establishment of an NFV network service link.

Embodiment 17

This embodiment provides a second communications unit 3500. As shown inFIG. 35, the second communications unit includes: a receiver 3502 and aprocessor 3503, where the receiver 3502 is configured to receive a routeand resource configuration request message, where the route and resourceconfiguration request message carries information about a service linktemplate through which a service route passes, to request to perform,according to the service link template information, route and resourceconfiguration for a VNF included in a service link in the service linktemplate, where the service link template information is used toindicate a correspondence between a service link identifier andinformation about a service link; and the processor 3503 is configuredto perform, according to the service link template information receivedby the receiver 3502 and information about a physical resource of aNFVI, the route and resource configuration for the VNF included in theservice link in the service link template.

The transmitter 3502 may be configured to: receive the route andresource configuration request message sent by an NFV orchestrator NFVO.

Further, as shown in FIG. 36, the second communications unit 3500further includes a transmitter 3504, where the transmitter 3504 isconfigured to: if the route and resource configuration succeeds, sendinformation indicating that the route and resource configurationsucceeds.

In this embodiment, the second communications unit may be a VIM, or maybe an NFVI controller, which is not limited in this embodiment. For arelated description of the NFVI controller, refer to the part of step501 in Embodiment 2. Details are not repeated herein in this embodiment.

For the method for service implementation in an NFV system that isperformed by the second communications unit, refer to a description ofEmbodiment 5 or Embodiment 6. Details are not repeated herein in thisembodiment.

Based on the second communications unit provided in this embodiment, thesecond communications unit receives a route and resource configurationrequest message, where the route and resource configuration requestmessage carries information about a service link template through whicha service route passes, to request to perform, according to the servicelink template information, route and resource configuration for a VNFincluded in the service link in the service link template; and thenperforms, according to the service link template information andinformation about a physical resource of an NFVI, the route and resourceconfiguration for the VNF included in the service link in the servicelink template, implementing a function of obtaining upper-layerinformation about a service link and guiding route and resourceconfiguration of the NFVI by using the upper-layer information about aservice link, and implementing establishment of an NFV network servicelink.

It may be clearly understood by a person skilled in the art that, forthe purpose of convenient and brief description, division of theforegoing functional modules is taken as an example for illustrating theapparatus described above. In actual application, the foregoingfunctions can be allocated to different functional modules andimplemented according to a requirement, that is, an inner structure ofan apparatus is divided into different functional modules to implementall or some of the functions described above. For a detailed workingprocess of the foregoing system, apparatus, and unit, reference may bemade to a corresponding process in the foregoing method embodiments, anddetails are not described herein again.

In the several embodiments provided in the present application, itshould be understood that the disclosed system, apparatus, and methodmay be implemented in other manners. For example, the describedapparatus embodiment is merely exemplary. For example, the module orunit division is merely logical function division and may be otherdivision in actual implementation. For example, a plurality of units orcomponents may be combined or integrated into another system, or somefeatures may be ignored or not performed. In addition, the displayed ordiscussed mutual couplings or direct couplings or communicationconnections may be implemented by using some interfaces. The indirectcouplings or communication connections between the apparatuses or unitsmay be implemented in electronic, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,may be located in one position, or may be distributed on a plurality ofnetwork units. Some or all of the units may be selected according toactual needs to achieve the objectives of the solutions of theembodiments.

In addition, functional units in the embodiments may be integrated intoone processing unit, or each of the units may exist alone physically, ortwo or more units are integrated into one unit. The integrated unit maybe implemented in a form of hardware, or may be implemented in a form ofa software functional unit.

When the integrated unit is implemented in the form of a softwarefunctional unit and sold or used as an independent product, theintegrated unit may be stored in a computer-readable storage medium.Based on such an understanding, the technical solutions essentially, orthe part contributing to the prior art, or all or some of the technicalsolutions may be implemented in the form of a software product. Thecomputer software product is stored in a storage medium and includesseveral instructions for instructing a computer device (which may be apersonal computer, a server, or a network device) or a processor(processor) to perform all or some of the steps of the methods describedin the embodiments. The foregoing storage medium includes: any mediumthat can store program code, such as a universal serial bus (USB) flashdrive, a removable hard disk, a read-only memory (ROM), a random accessmemory (RAM), a magnetic disk, or an optical disc.

The foregoing descriptions are merely specific implementation manners,but are not intended to limit the protection scope. Any variation orreplacement readily figured out by a person skilled in the art withinthe technical scope disclosed shall fall within the protection scope.Therefore, the protection scope shall be subject to the protection scopeof the claims.

What is claimed is:
 1. An operations support system/business supportsystem (OSS/BSS), comprising: a processor; and a non-transitory computerreadable storage medium storing a program for execution by theprocessor, the program including instructions to: obtain service linktemplate information, wherein a service route passes through the servicelink template, and wherein the service link template informationindicates a correspondence between a service link identifier andinformation about a service link; and send the service link templateinformation to a network function virtualization (NFV) orchestrator(NFVO), so that the NFVO can request to perform route and resourceconfiguration for a virtualized network function (VNF) in the servicelink according to the service link template information.
 2. The OSS/BSSaccording to claim 1, wherein the instructions further compriseinstructions to: receive information indicating that the service linktemplate information has been received.
 3. The OSS/BSS according toclaim 1, wherein the instructions further comprise instructions to:receive information indicating that the route and resource configurationhas succeeded.
 4. A network function virtualization (NFV) orchestrator(NFVO), comprising: a processor; and a non-transitory computer readablestorage medium storing a program for execution by the processor, theprogram including instructions to: receive service link templateinformation, wherein a service route passes through the service linktemplate, and wherein the service link template information indicates acorrespondence between a service link identifier and information about aservice link; and send a route and resource configuration requestmessage to request to perform, according to the service link templateinformation, route and resource configuration for a virtualized networkfunction (VNF) in a service link in the service link template, whereinthe route and resource configuration request message includes theservice link template information.
 5. The NFVO according to claim 4,wherein the instructions further comprise instructions to: send theroute and resource configuration request message to a secondcommunications unit, to request the second communications unit toperform, according to the service link template information, the routeand resource configuration for the VNF in the service link in theservice link template.
 6. The NFVO according to claim 4, wherein theinstructions further comprise instructions to: send informationindicating that the service link template information has been receivedin response to receiving the information about the service linktemplate.
 7. The NFVO according to claim 4, wherein the instructionsfurther comprise instructions to: receive information indicating thatthe route and resource configuration has succeeded in response to theroute and resource configuration succeeding.
 8. A method comprising:obtaining, by an operations support system/business support system(OSS/BSS), service link template information, wherein a service routepasses through the service link template, and wherein the service linktemplate information indicates a correspondence between a service linkidentifier and information about a service link; and sending the servicelink template information to a network function virtualization (NFV)orchestrator (NFVO), so that the NFVO can request to perform route andresource configuration for a virtualized network function (VNF) in theservice link according to the service link template information.
 9. Themethod according to claim 8, wherein the method further comprises:receiving information indicating that the service link templateinformation has been received.
 10. The method according to claim 8,wherein the method further comprises: receiving information indicatingthat the route and resource configuration has succeeded in response tothe route and resource configuration succeeding.
 11. The methodaccording to claim 10, further comprising sending, by the OSS/BSS to acommunications unit, the information indicating that the route andresource unit has succeeded.
 12. The method according to claim 8,wherein obtaining information about the service link template comprisesreceiving, by the OSS/BSS from a communications unit, a route andresource configuration request message.
 13. A method comprising:receiving, by a network function virtualization (NFV) orchestrator(NFVO), service link template information, wherein a service routepasses through the service link template, and wherein the service linktemplate information indicates a correspondence between a service linkidentifier and information about a service link; and sending a route andresource configuration request message to request to perform, accordingto the service link template information, route and resourceconfiguration for a virtualized network function (VNF) in a service linkin the service link template, wherein the route and resourceconfiguration request message includes the service link templateinformation.
 14. The method according to claim 13, wherein sending theroute and resource configuration request message comprises: sending theroute and resource configuration request message to a secondcommunications unit, to request that the second communications unitperform the route and resource configuration for the VNF in the servicelink according to the service link template information.
 15. The methodaccording to claim 13, further comprising: sending informationindicating that the service link template information has been receivedin response to receiving, by an NFVO, information about the service linktemplate.
 16. The method according to of claim 13, wherein the methodfurther comprises: receiving information indicating that the route andresource configuration has succeeded in response to the route andresource configuration succeeding.
 17. The method of claim 16, furthercomprising sending, by the NFVO to a communications unit, theinformation indicating that the route and resource configuration hassucceeded.